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.
Universe in BO - This will have the metadata and the data of all the tables . Effectively , for the BO reporting , this universe will act as the data source.
We are trying to simulate the universe using the the joiner functionality joining all the mas files based on the relationship.We have a question like can this increase the performance (since that webfocus mas files doesnot have the data withit) or can the universe be simulated with the webfocus join?? or is there anyother way ?
And another question is , Can we get the ER model (Data Model) within webfocus ?This message has been edited. Last edited by: Kerry,
If your tables are in Oracle then you would be better creating views in Oracle and generating your WebFOCUS masters against the views than creating large joins directly against the table.
It would also have the advantage that you can generate the ER model very easily.
If you use the join tool in WebFOCUS to build your joins then you will get a basic ER model from that.
However instead of trying to replicate your BO Universe in WebFOCUS do an analysis of your reporting requirements and optimize your datamart for that. A much more efficient approach.
There is a Business View in WebFOCUS that is more efficient than a bunch of JOINs. See the Describing Data With WebFOCUS Language manual and do some searching on FOCAL POINT
Reporting Server 7.6.10 Dev. Studio 7.6.8 Windows NT Excel, HTML, PDF
I agree with JG. If you use Teradata views, those are optimized by the DBAs who set them up. Indexes can be added to them as well. This is critical for Teradata as it is a data base that often hold gigantic amounts of data.
At the shop that I'm at, we are only allowed to use Teradata views. Some of them are views on base tables but many of them are business models. In any event, many of them hold millions of rows each.
Just be careful and make sure to trace your queries.