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.
Use the user or group profiles to set APP PATH accordingly. For development this is a bit more tricky and you will have to use AppLock feature.
To run .prf with dots in you will have to get edasprof to check the userid see if the profile is there and run it explicitly unless this now fixed in 7.6
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
You don't mention if your backend environment is Windows or some other platform. If it is Unix, I can explain, if you want, how we secure a huge (over 500 directories) self service implementation for a variety of user groups whose work needs to stay separate and untouchable by developers not in their specific group.
Not sure how you would do that in Windows. But if you want more detail, I'd be happy to share.
Yes, unfortunately for you, we do make very liberal use of Unix file and directory permissions.
As for APPLOCK, it is not a command per se. Please see section "Restricting the Use of APP Commands" in the Server Administration manual. Yours would be UnixNtAsOpen_SrvAdm76x.pdf (I don't know if there is one for 762, haven't downloaded it yet, am using 761).
You need to be careful about using this feature in a self service environment, though. We decided against it because it restricts the use of many of the APP commands, including APP PREPENDPATH. The way our environment is set up is that we have a global profile, edasprof.prf, that points to all the generic master file directories that everyone has access to. Then each user has a profile with APP PREPENDPATH to point to his or her specific directories. The command is also coded in programs because many programs are run from a browser using a default id which only has access to the directories in edasprof.
Can you do something with directory share permissions in Windows?