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.
With Essbase, wouldn't you have to rollup the database and store it in the Essbase cube? With Hyperstage, you do a bulkload from your other systems and you are ready to go.
Posts: 229 | Location: New York | Registered: July 27, 2004
Okay, so I would consider a "cube load" versus a "bulkload" to be equivelent. I guess, from the lack of response, that no one has ever tried or seen a comparison. That would be one issue I would be interested in.
A second question would concern data access- Hyperstage data may be accessed via IA (now) and ID; I don't have any sense as to how EssBase cubes are primarily accessed- but does anyone have any experience comparing that access with IA/ID Hyperstage access?