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.
Hello We are moving WebFOCUS from W2K environment to Linux. Most of our reports are self-serve and currently we have 10 application (server side) folders. We are debating whether to create 50-60 different application folders in the new Linux environment based on each report.
Is this a good practice? Is there a limit of number of app folders? Is there a limit on the total length of app path? Also, can we have second level folders below the APP? eg. App\Fin\AcPayable?
I will appreciate your help. Thank you,This message has been edited. Last edited by: Kerry,
I can't really say what a "best practice" is in terms of number of application folders but 50-60 looks a bit high for my own taste.
The more application folders you have, the more level of control you can have in terms of security (by limiting access to certain procedures and master files, for instance) but that may also mean a higher effort in maintaining your user/group profiles. I think only your reporting needs can drive this decision as long it's something your team feels comfortable at maintaining.
In regards to second-level folders, there is a new feature in WebFOCUS 7.7 called nested applications which may be just what you need.
In one of our webfocus environments we have over 100 application folders. This is a shared environment and each application has a directory. We do not put most of the folders in the server app path but require developers to use the APPPREPENDPATH in their code to make sure they are getting the masters their application needs.
We do it this way on this set of servers so that the applications are self contained.
Webfocus 8.0.7 on Windows
Posts: 176 | Location: Ohio | Registered: October 26, 2006
I assume then that you have just a few app folders (which pretty much everybody can access) to put your "launch" .fexes and each of these procedures then set the APP PATH according to what they need.