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.
In WebFOCUS 7 and prior we had a few reports that were accessible via direct web link from in-house web-based systems. These systems created a web link that included the Explicit Signon using the IBIMR_action=MR_SIGNON and included the credentials for signon in the URL. This was an internal-only system - not a recommended practice for obvious security reasons. This was used to display BI reports related to the data the users were looking at on the in-house system without having them log into BI.
An example would be where my Requisition system allows a user to run an WebFOCUS accounting report displaying GL Balances for a department & account from an expense requisition displayed within the Requisition system. The WebFOCUS report is displayed in a popup window. The user has no idea this is coming from the BI reporting system since s/he hasn't had to log into a WebFOCUS account.
I can't find where the Explicit Signon is available from WebFOCUS anymore, so I assume it is replaced with a better, more secure approach. The only approach obvious to me would be to utilize the "Public" application to duplicate these report procedures, or grant "Everyone" access specifically to these few reports.
Now that you are using version 8 of WebFOCUS - we are on 8.1.0.4 - what method is your team using for internal web-based (not WebFOCUS) systems/applications to invoke/display a BI report from your WebFOCUS server with specified parameters in a browser window when the user will not have a signon into your WebFOCUS system?This message has been edited. Last edited by: <Emily McAllister>,
WebFOCUS 8.1.0.4 Win Server 2012, Excel, PDF, HTML
Posts: 8 | Location: Paris, IL USA | Registered: December 08, 2009
In WF 7.x we used Managed Reporting Explicit Sign-on Processing as well.
For 8.0.07, we worked with our IB Tech Rep, and determined that in WF 8 the RESTful Web Server Request 'IBIRS_action=signOn', replaces the WF Servlet Request 'IBIMR_action=MR_SIGNON', for the Explicit Sign-On.
A RESTFul request looks similar to the WF MR servlet request. Something like: