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 email@example.com for further assistance. Reference the community FAQ to learn more about the community.
Basicallly i need to apply the DBA security. after creating mdf profile and doing all the stuff required for it and then i run my master file ideally it should filter the data but when i do that i am getting error where i have used &IBIMR_memberof variable. So i guess the server is not recognising the variable. Also i have passed the users and the groups from client to the erver in administrative console settings.
Webfocus 8.x Windows PDF,HTML,XLSX
Posts: 58 | Location: India | Registered: June 01, 2018
In general, it sounds like you want to rely on how a Users's Security is set up in the Client (via Security center groups).
The catch is that if you're running straight off the WF Reporting Server, it doesn't know much of anything about the client Security setup. It only knows how the security is set up on the WFRS (WebFOCUS Reporting Server). You can create users and groups on the WFRS to function sort of like what you see over in the Security Center of the client.
You're not really stuck if you're using External Security (like Active Directory for example) to know what Groups a person belongs to. If you use AD on the Client side and "MAP" an external Group to a WF Group, you can use that same concept on the WFRS directly. It's a little extra work.
Let me ask a question though. Are you really going to let users run directly from the WFRS (as we used to do with "self service" applications pretty often)?
If you're always going to come from the client, or new enough report caster, the client variables &FOCSECUSER and &FOCSECGROUP are something you could use.
My guess is that you're using site.wfs on the client to populate the missing value you're seeing on the WFRS.
There's an older paper that is really geared toward making Software as a Service applications and how you'd handle security there, but it talks about the relationship between the Client Security Center and the WFRS groups / users. Might be worth a look: