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.
“on demand paging” checked. But still takes the same time to get the result. Why?
I checked “on demand paging” check-box. (just as SET WEBVIEWER = ON in version 5.2.8).
But WebFocus still takes the same time to get the data. Is there any way that we can solve this problem – just search/ read in part of the data in tables. So WebFocus will not take long time for the long report.
Hi Lisa How quickly the first page can be shown depends totally on the complexity of the report processing as well as the size of the answer set. The limitation is that the full report needs to be already available on the Reporting Server before the first page can be sent to the WebFOCUS client (and from there, to the browser). This is why you may not be seeing better performance. Regards, Rich
WebFOCUS 8202 Win 2012 Test - WebFOCUS 8203 on Win 2012
The full report is still materialized by the reporting server, then delivered page at a time from the Web tier to the Browser. ODP saves rendering time on the browser (imagine a 100 page HTML), not server access time.
Record limit works well... So does deesigning your reports with "major BY" at a time in mind. I've done reports that have a next/previous hyperlink in the summary/heading to get the next/previous major BY field. Each NEXT runs the report again with a different selection criteria. One catch, a PREVious also runs the report again too...
Brian Suter VP WebFOCUS Product Development
Posts: 200 | Location: NYC | Registered: January 02, 2007