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.
I am trying to get the userid of the user logged in to Webfocus, but what I am doing is always returning 'wfadmi'. (No, that's not my userid.) Is there a different way to do this?
-SET &USR = GETUSER(USERID);
-TYPE &USR
This message has been edited. Last edited by: <Kathryn Henning>,
WebFOCUS 7.6.9 Windows all output (Excel, HTML, PDF)
What Waz is asking has great relevance as it all depends on your particular infrastructure and WebFOCUS components involved.
In my case for instance, we use LDAP authentication to Active Directory on both WebFOCUS Reporting Server and Client.
On the WF Client's Custom Settings (accessible via the WebFOCUS Administration Console > Configuration > Custom Settings), we have the following:
<SET>IBIMR_user(pass)
That allows us to use &IBIMR_user anywhere in our code to determine who is connected.
Being usually on the paranoid side, I prefer to test for the existence of that variable first, falling back on GETUSER() otherwise. This is what I use in the "common" portion of my procedures:
-* Determine connected user ID
-IF &IBIMR_user.EXISTS THEN GOTO :_IBIMR_user;
-SET &IBIMR_user = ' ';
-:_IBIMR_user
-SET &I_USER_ID = IF &IBIMR_user EQ '' OR ' ' OR '.' THEN GETUSER('A80') ELSE &IBIMR_user;
-SET &I_USER_ID = TRUNCATE(&I_USER_ID);
-TYPE Welcome &I_USER_ID !
That way, I can "trust" that &I_USER_ID (my own internal variable) has a valid content I can use for logging or any security-related purposes.