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 are trying to address the issue of long run times for reports from our portal. The problem is that reports will crash if they take longer to run than the IIS (or whatever server) timeout setting. For example in our setup we have IIS set to max 5 mins. After 5 mins the report dies.
What we would like to do is have a timer running in javascript after the report is submitted and after 4:58 has elapsed we will redirect the report as deferred mode.
Has anyone accomplished this? I had an old case open about it and I was instructed as to how to increase the IIS timeout setting. That, of course, is not what we want to do. Some of the reports could take one hour or one minute, depending on which params are selected as well as what else is going on on the servers at the time. We want the maximum flexibility. The bottom line is that the user might not know how long it will take and we don't want him to wait for 5 mins and then see an ugly error screen.
I will start experimenting with a javascript timer and document.form.submit with changed params... just wondering in advance if anyone else is doing this...
One thing you could do is force all jobs to run only as deferred and then the user can access the deferred status screen to check on the status of the job. No matter how long the report takes to run they can access it from there. Another option and an Add-on to WebFOCUS is Resource Governor. This builds a knowledge database on the statics on how long jobs run, what where statments, field, ... Then you could build Rules that say things like if the average elapsed time is greater then say 4 1/2 minutes send a message back to the user and tell them to run the job deferred.
the way we've done it is to have a standardised layout of our parameter pages with 2 buttons, Run Report and Run Deferred. Each button calls a JavaScript which submits the form. I suppose you have some kind of idea of the average run time for each report. If it exceeds say 4 min, disable the Run Report button and only allow the users to run deferred. Maybe store the run time in some table and display it on the form. I know this is not exactly what you asked for, and if you do find a method to automatically redirect a job to deferred, I would be more than interested to know how.
Posts: 319 | Location: Stockholm, Sweden | Registered: February 04, 2004