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.
Thank you in advance for taking a look at this. -*------------------------ Customer has three WebFOCUS environments; DEV, QA and PROD.
Objects (fex,htm,sty,mas,acx) are created in DEV, promoted to QA then PROD.
Customer does not want to edit the files after they have moved from DEV to higher environments
Consider the following two example acx files, the issue is in each environment the db_owner is slightly different. For other Oracle reasons, they can not make the db_owner the same name.
The question is, can we have a variable db_owner name as illustrated in the 2nd example?
Everything is the same, except the db_owner. THe "TABLENAME=" is the only difference. The goal being, don't change a thing once it leaves the DEV environment.
BTW, this isn't SQL Passthru.
So you guys use something like?
SET CONNECTION_ATTRIBUTES dbasename/user,password
This isn't a show stopper, just a nice to have feature. Its really a simple issue, one minor thing to change during the process and there maybe around 100 MDF files total. But, the group that promotes are not developers, they wouldn't necessarily see a problem if they made a mistake.
Another idea is automate this change, run a script, post promotion into each env. That would eliminate human error.
[SOLVED] Actually, an unrelated issue with the complexity of the GOLD Database forced us into SQL Passthru and it became a non-issue for moving forward.