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.
A number of WebFOCUS customers and potential RStat customers lately have asked if RStat can be architected differently from its default setup. These architecture questions came as a result of some customers’ requirements to not allow data on local a machine or to utilize consolidated development environments. Production or deployment environments are only a concern if the solution is to leverage the additional R packages not currently accessible through the RStat GUI.
So we conducted tests of the distributed architecture, and also tested other aspects of the tool, such as concurrent logon to RStat and execution of RStat functionality, as well as performance. The goal of the testing was to determine if RStat can be architected for a distributed development environment and what, if any, limitations exist.