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.
We have a BI Dashboard where Global (&&) variables are important. It seems like if we leave the screen open for some period of time with no interaction on the dashboard, and then click a link to run a fex, the global variables no longer exist. But the fact that we woke something up by running that fex seems to make the variables available to subsequent requests.
Any ideas?
Thanks,
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
It has been a while, but the globals are stored in a file in the temp directory of the client installation. The _TempFileTimeout is defaulted to 900 seconds. That means that the global variable file is then deleted after 900 seconds after it is created. The global file is re-created every time you run a request. However, after 15 minutes of inactivity, it would be deleted. I believe that if you change that value to the same number as the session timeout, then you might stop this.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott