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.
Our site has a license for Resource Analyzer; for various reasons we've hadn't yet enabled/configured the product.
Is your site, or sites you've consulted with, using RA successfully/happily, and finding it helpful?
A forum search of 'Resource Analyzer' gives 147 hits, but unfortunately the vast majority of the threads basically state 'If you want to know who is using your system and how, think about gettting WF/RA'. :-)
It looks like the most recent release of the RA manual is 7706. Is that the most recent release available as well?
The RA reports shown in the manual, look like they would be very useful.
Some threads seem to talk about storing the RA data in a FOCUS database. Is that because the ability to store the data in a relational database is new?
Other threads talk about RA overhead. Again, is that an issue with previous versions of RA?
Any experiences/sharing welcome.
Thanks all!
Pilot: WebFOCUS 8.2.06 Test: WebFOCUS 8.1.05M Prod: WebFOCUS 8.1.05M Server: Windows Server 2016/Tomcat Standalone Workstation: Windows 10/IE11+Edge Database: Oracle 12c, Netezza, & MS SQL Server 2019 Output: AHTML/XLSX/HTML/PDF/JSCHART Tools: WFDS, Repository Content, BI Portal Designer & ReportCaster
The latest doc for RA is https://webfocusinfocenter.inf...appent/pdfs/i_ra.pdf marked Version 7 Release 7.07. That's Server versioning which translates to WebFOCUS Reporting Server 8.201. The doc is dated November 2016.
WebFOCUS 8206, Unix, Windows
Posts: 1853 | Location: New York City | Registered: December 30, 2015
Well, there is a plethora of possibilities of gathering user data. On a total full setting you basically are running ECHO=ALL as well as the data... Which will get your database filled up faster than you can imagine. Performancewise imagine running with a edalog set on debug with all traces on with the added database i/o...
OK, so now that I have scared you properly, so you just don't go turn it on and go huh? I can tell you that I've had to set up some "paranoid 1984 reporting" which had to be able to report if a user had performed an adhoc query, and what the return was, retention 5 years was it... Thankfully small recordsets, but you can get the RA tweaked to do this kind of things as well. Trend data is way easier, but you need to again think what data you want to keep/follow - answer is not all, and who is going to use it and for what. So, running meaningful reports needs also to be planned.
Using a FOCUS database on disk vs. database table, depends where you have space available. In any case it should be separate from the rest and expandable, so you don't crash on running out of space or disk or bottleneck on the i/o.
If you are running trends, and follow large datasets, run the weekly/daily/monthly data aggregates and then purge the old data - your numbers wont change, and keeping the aggregate rows takes way less space than raw data.
As with most, RA is a good tool, but you need to plan its use really well.This message has been edited. Last edited by: Hank W.,
Cheers, H. WebFOCUS 8.1.05M Oracle 11g - DB2 RedHat
Posts: 115 | Location: Brighton UK | Registered: February 19, 2005
@Hank - Thank you so much for the share. Yep, being careful about exactly what we decide to log, setting up purges, example of a use case, & need for planning is exactly what I was looking for.
Pilot: WebFOCUS 8.2.06 Test: WebFOCUS 8.1.05M Prod: WebFOCUS 8.1.05M Server: Windows Server 2016/Tomcat Standalone Workstation: Windows 10/IE11+Edge Database: Oracle 12c, Netezza, & MS SQL Server 2019 Output: AHTML/XLSX/HTML/PDF/JSCHART Tools: WFDS, Repository Content, BI Portal Designer & ReportCaster
I tried setting it to go to a SQL server db in 8105 and it took so long to load the results each day that it would not finish the previous day before starting the next. By the time I cut back what it was gathering enough to make it work, the data was less valuable. I'm just using Tealeaf now
8105 Tomcat and AIX reporting server input: Teradata, SQL, DB2, Essbase, Oracle, text output:html, excel, PDF,
Some threads seem to talk about storing the RA data in a FOCUS database. Is that because the ability to store the data in a relational database is new?
Hi David, The company that i work for now has been using relational database with RA for few years now . We do a nightly archive job which updates the stats into oracle everyday. I believe if you using Relational DB for repository , the RA table will also be stored in the same db.
Thanks, Aswin RavikumarThis message has been edited. Last edited by: Aswin Ravikumar,
Webfocus 8.1 Windows x64 Excel
Posts: 39 | Location: Pittsburgh | Registered: July 25, 2017
Just as an FYI in addtion to Resource Analyzer there is also a new offering called the Enterprise Usage Monitor that uses the edaprint.log(s) as the source to providing a lot of useful information about WebFOCUS usage.
Thank you for using Focal Point!
Chuck Wolff - Focal Point Moderator WebFOCUS 7x and 8x, Windows, Linux All output Formats
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005