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.
I'm new to WebFocus/ReportCaster and have been handed an undocumented older version of WF, ReportCaster and the BI Dashboard. We are having an issue with user's requesting reports that are huge (10+MB) and hosing our server resources and ultimately dragging down disk space. I need the quickest, easiest way to remedy this as apparently original developers did not bake in any rowcount/size limitations into report requests. Is there a way to restrict the size of a request from the dashboard and display a message to the user they have exceeded the size request parameters? Any help, or direction to online help manuals for this type of coding is appreciated!! Thanks!This message has been edited. Last edited by: Kerry,
In my opinion output reports of that size should always be avoided, since people tend to download all the data and use excel to create reports. I think you should create reports that do give information and not raw data, so it should never be that huge Drill down at lower level should give some details.
Restricting end user to only partial information would not give the information one need.
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
Posts: 2387 | Location: Amsterdam, the Netherlands | Registered: December 03, 2006
Report size can be limited by General or user specific WHERE statements, record read limit, or record output limits. You could also invoke rules through the use of Resource Governor. Your disk space problem could also be caused by temporary files left behind by badly terminated reports or log file settings that don't limit the size or number of log files created. If you bounce the WebFOCUS Reporting Server you will regain the space lost to these temporary files.
WF 7.7.04, WF 8.0.7, Win7, Win8, Linux, UNIX, Excel, PDF
Posts: 175 | Location: Pomona, NY | Registered: August 06, 2003
You might like SET WEBVIEWER = ON so that the report is brought back to the browser 1 page at a time. Yes to your question about limits; if in your original fex, you HOLD the initial extract file, you can test for the size of that file before you decide if it is reasonable to present the results to the user. TABLE FILE CAR PRINT MODEL ON TABLE HOLD END -RUN -SET &howmany = &LINES ; -IF &howmany LE 100000 GOTO rep.gen ; -TYPE Dude, you've just asked for &howmany records; way too many; Refine your parameter selection, and try again -EXIT -rep.gen TABLE FILE HOLD ... do some nice styling and present results to user END
In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
There would have to be a caveat on this, as it should depend on the type of report being produced.
Consider PDF reports, these are formatted and can contain much information, then add images, logos, etc. This will make an even larger report. They can get quite large.
You need to be very carefull about any blanket restrictions on output.