As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
If I understand properly, you now have a DB that will take over if the main one "crash".
I may be wrong, but you should have nothing to do.
In WF you define an "adapter" which point to a server (who has to be a DNS instead of the physical IP), then if the main DB crash, it should have an automatic take over from the other DB (the fail over one) and that one should have the same DNS name. So it should be transparent for WF.
We have something similar here with High Availability where I only have one connexion string (adapter) that point to a DNS and once a month the network team switch the "live" server with the "backup" server and I see nothing.
But I may have misunderstood your question or have answered wrong.
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
Yes it may need some work to define the DNS but it will have to be done once.
Except if I'm wrong, using the DBA info, you may need to update those lines of code (if whenever something change) everywhere they will exist while one place will have to be changed (DNS) with the DNS solution and it won't be "your" call: no effect in WF/java code.
I'm not an expert on that question, but I don't need to be a Einstein to see that the solution must reside as closer as possible of the source...
WF versions : Prod 8.2.04M gen 33, Dev 8.2.04M gen 33, OS : Windows, DB : MSSQL, Outputs : HTML, Excel, PDF In Focus since 2007
Posts: 2409 | Location: Montreal Area, Qc, CA | Registered: September 25, 2013
If it's really just a matter of toggling the CONNECTION= value in the access files of the synonyms, the value can be globalized, and you can engineer the profile that establishes the && variable to determine which connection to use.
That's a standard practice to avoid textual changes when migrating synonyms across environments, and can be utilized here as well.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005