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 firstname.lastname@example.org for further assistance. Reference the community FAQ to learn more about the community.
In my experience, BASEAPP is always part of the APP PATH. If it is not specifically listed, it seems to be the last folder in the app path. The search order seems to be APPHOLD, APP PATH folders in the order listed then BASEAPP. I have not come across (or searched for) documentation that supports this, but this is how it seems to work.
In FOCUS since 1985. Prod WF 8.0.08 (z90/Suse Linux) DB (Oracle 11g), Self Serv, Report Caster, WebServer Intel/Linux.
Posts: 975 | Location: Oklahoma City | Registered: October 27, 2006
I thought the user profile would only limit them on the self service side but, not on the MRE. My challenge is to limit the MRE users with certain APP Folders when 1. They use Report Assistant to browse Masters 2. They use editor to TABLE FILE.
Any ideas would be greatly appreciated.
Posts: 289 | Location: Houston,TX | Registered: June 11, 2004
Here is what we came up with... The basic premise on how our system is set up is that we limit access to masters based on the Application Directory they are in.
We use group-level profiles that are executed when a user logs on. In the profile we do four things 1) We build an APP PATH statement with three variables a) &&PSRPATH - this contains application directories the user group needs based on the way they subscribe to our data b) &&MYPATH - this contains the name of an application directory that is specific to the user group/domain name c) &&FILTERPATH - this contains the names of application directories that have masters we want the users to have 'indirect' access to. By that I mean these datasources are accessed from HTML pages that act as the UI for some of our applications. We do not want users writing their own reports against these masters though. 2) We INCLUDE a 'filter' fex. This file declares filters against any masters a user may encounter whether it is through one of our applications or through one of the web tools (ReportAssist, GraphAssist, InfoAssist, etc.) If we don't include the application directory in the APP PATH statement we aren't able to declare a filter on the masters in that directory. 3) We set the value of &&IBI_IF_APPS by setting it to the physical path to an 'apps' fex. This file works similarly to the APP PATH statement but it has different syntax. We do this because the list of masters available in the web tools is not determined by APP PATH, it is determined by the value of &&IBI_IF_APPS. Here we build the list of application directories the user can access based on &&PSRPATH and &&MYPATH. &&IBI_IF_APPS is also used in the data upload utility. Therefore it is important that we disable write access to all the application directories except the one specified in &&MYPATH so the user doesn't save a file to a commonly used application directory. 4) We set the value of &&IBI_IF_FLDS by setting it to the physical path to a 'fields' fex. This file determines what fields within each master a user has access to. Most of the time we don't limit fields but when we need to this is where we do it.
To summarize, we use APP PATH because it is required in order for us to declare filters. We use &&IBI_IF_APPS because it is required to control master file access in the web tools.
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007