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.
SESSION_EXPIRATION: If this parameter is set to 20 mins, does it imply that irrespective of the user perfroming some action, once the session is initiated, the session is going to expire after 20 mins or does it mean that the session is active for another 20 mins every time the user performs some action ? (I am currently working on an application which has a launch page for a set of reports, so this scenario pops up if the user selects one report and then it is left idle for sometime. Then he comes and runs an another report from the launch page)This message has been edited. Last edited by: Kerry,
This is nothing to do with an enduser. It relates only to the WebFOCUS server console.
If endusers are getting timeouts in a standard WebFOCUS session then check the value of WF_COOKIE_EXPIRATION in the WebFOCUS administration console (not the server console). If the problem is in dashboard check USER_MAX_INACTIVE in web.xml.
Any timeout means if the user takes no action the timeout comes into effect. if the user does perform some action the timeout is reset.
As I said SESSION_EXPIRATION has TOTALLY nothing to do with your problem.
A user session will stay active as long as the user is logged on to WebFocus and the WebFOCUS cookie has not expired.
This is controlled by the WF_COOKIE_EXPIRATION cookie as I explained.
If a user logs off the cookie expires and no further reports can be run unless
a) The user logs on again. or b) You pass the logon id and password as part of your URL.
If you set WF_COOKIE_EXPIRATION to a specific time then that deletes the cookie and effectively logs off, however if you pass the logon id and password as part of your URL then that effectively does an automatic logon.