11g E-Business Suite LogoffURL In Instanceconfig.xml Gets Removed After Restart Of BIEE Services
Last updated on SEPTEMBER 20, 2013
Applies to:Business Intelligence Server Enterprise Edition - Version 188.8.131.52.2 and later
Information in this document applies to any platform.
Using E-Business Suite (EBS) integrated security, users would like to navigate back to EBS homepage when logged out from OBIEE.
- Configured logonURL and logoffURL in instanceconfig.xml using SchemaExtensions element. However, the schema extension gets wiped out every time a deployment of a new web catalog is done.
- Changed authenticationschemas.xml and instanceconfig.xml per the OBIEE 11g security guide, "Oracle® Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1)".
<Schema name="EBS-ICX" logonURL="http://servername.com:8052/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE" logoffURL="http://severname.com:8052/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE"/>
This works once changed manually, but again manual changes are wiped out upon BI system restart.
- Tried updating EM directly to enable SSO and provide the logon/logoff URLs. The idea being EM will then maintain the configuration file and the needed settings will not be wiped out upon restart.
- Checked "enable SSO", and in the list providers, only "Custom" is a viable choice. Chose "Custom" as SSO provider. Then it generated the following SchemaExtensions. Note this SchemaExtension is not specific to EBS-ICX schema. Because of that it was not effective. After a restart of the services, and logon then logoff, it did not go to LogoffURL.
<!--This Configuration setting is managed by Oracle Enterprise Manager Fusion Middleware Control-->
<Schema logonURL="http://servername.com:8052/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE" logoffURL="http://servername.com:8052/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE"/>
Because the SchemaExtension is not named with EBS-ICX, it did not work.
The working version is as follows. The name="EBS-ICX" attribute is needed.
<Schema name="EBS-ICX" logonURL="http://servername.com:8052/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE" logoffURL="http://servername.com:8052/OA_HTML/OA.jsp?OAFunc=OAHOMEPAGE"/>
Restarting BI does not remove the non-working, incorrect SchemaExtensions. Instead the incorrect update is left in the file.
Enabling SSO in EM and setting the logon/logoff URLs does not update the instanceconfig.xml file. However, the instanceconfig.xml file has a modified date of when the enable SSO changes were activated. An attempt by the system to update the file was made, but did not complete as there are no actual updates.
This is the only SSO related entry in the file:
The SSO enable update did not go in.
Do see the EM page as showing SSO enabled and a logon/logoff URL entries are there.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms