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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
Stored procedures are not portable between different RDBMSs. A stored procedure written for SQL*Server will not work on Oracle/DB2/etc since the stored procedure languages are different.
*IF* you are developing a brand new system *AND* there is any possibility that you will need to migrate/port your system to a different RDBMS in the future, then you should consider putting the logic of your procedures into WebFOCUS. WebFOCUS can do pretty much anything that a stored procedure can do and it is portable between RDBMSs (of course you may have to make adjustments if you are using a datatype in one RDBMS which is not available in the other.)