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.
Does anyone have a Java front-end to their application and is capturing the fact that reports time out or something similar and communicate a message back to the user that is running the report on-demand to let them know that the report has timed out or whatever? If so, could you please explain how you are doing this?This message has been edited. Last edited by: Kerry,
It could be a number of things causing the timeout....the report itself, the connection, or etc. I wanted to know if there were anyone out there with a java front-end that captures the fact that the report is timing out for any of these reasons and displaying a message back on the screen to inform the user that it has timed out.
I know Analyzer/Governor will capture as far as WebFOCUS is concerned. Howver, I wanted to know if anyone is capturing this maybe with java....which could be caused by anyone of the reasons above...not just because the report is taking a long time to run.
The main problem I see here is that without knowing what's causing the time-out (we're seeing something similar), it's kind of hard to capture the fact...
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :