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.
Wondering if anybody had some creative work-arounds for bugs involving either SIGNON_CORRECT or WF_SIGNON_MESSAGE settings.
Issues are in 5.2.1-3 SIGNON_CORRECT can not be set in site.wfs as documented and server name is preappended to WF_SIGNON_MESSAGE value and can't be controlled.
I guess at least one of these bugs is fixed in 5.2.6, but was curious if anybody had ideas outside of upgrading.