Last updated on SEPTEMBER 19, 2016
Applies to:Business Intelligence Reporting and Publishing Option - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Please see: Document 1993210.1 - OBIEE To Essbase Supported and Recommended Authentication Method and Release notes: Section 44.4.14, "Configuring SSO for Essbase and Hyperion Financial Management Data Sources With Oracle Business Intelligence 184.108.40.206, 220.127.116.11, and 18.104.22.168.2"
You are trying to setup shared SSO token between OBIEE (22.214.171.124.x)and Essbase (126.96.36.199) by following steps outlined in the System Administrators Guide:
Steps followed :
188.8.131.52 Enabling Oracle Business Intelligence to Generate or Accept a Hyperion SSO Token when Connecting to Essbase, HFM, and EPM Workspace Release 184.108.40.206 or Later
Before enabling to generate or accept a token, see Section 11.6.1, "Prerequisites for Configuring to Use Tokens."
To configure Oracle Business Intelligence for shared token generation when connecting to Essbase and Hyperion Financial Management and to accept tokens when integrated into EPM Workspace Release 220.127.116.11 or later (installed with the EPM System Installer), you first run the runRegSyncUtil utility, then you run an epmsys_registry command.
To enable Oracle Business Intelligence to generate or accept a Hyperion SSO token:
Locate the regSyncUtil_OBIEE-TO-EPM.zip file in the BI_ORACLE_HOME/common/CSS/18.104.22.168 directory and extract it to the same location.
Copy the reg.properties file from the system where Essbase or Hyperion Financial Management is installed:
to the following location on the system where Oracle Business Intelligence is installed:
On Linux systems, make runRegSyncUtil.sh executable using the following command:
chmod +x runRegSyncUtil.sh
Open runRegSyncEditUtil.sh (or runRegSyncEditUtil.bat on Windows systems) for editing. You can find the runRegSyncEditUtil file in the BI_ORACLE_HOME/common/CSS/22.214.171.124/regSyncUtil directory.
In the file, update the ORACLE_HOME and ORACLE_INSTANCE environment variables as appropriate for the given Oracle Business Intelligence environment. Note that ORACLE_HOME should be equivalent to MW_HOME/Oracle_BI1 and ORACLE_INSTANCE should be equivalent to MW_HOME/instances/instancen.
Save and close the file.
Run the utility. The following example shows how to run the utility on Linux:
Run the following epmsys_registry.sh command:
BI_ORACLE_INSTANCE/config/foundation/126.96.36.199/epmsys_registry.sh removeproperty SHARED_SERVICES_PRODUCT/@applicationId
Restart the BI Domain, including the Administration and Managed Servers.
Restart all OPMN processes.
If the BI Domain has the "virtualize" property set to "true," then perform the following steps to set a system property that enables the CSS to use the appropriate attribute for GUIDs:
In the MW_HOME/user_projects/domains/bifoundation_domain/bin directory, edit the setDomainEnv.sh file on UNIX or .cmd on Windows using the syntax appropriate for your operating system and shell.
Add a Java system property after the EXTRA_JAVA_PROPERTIES line, as shown in the following example for the Windows platform:
When you integrate with EPM System Release 188.8.131.52, add the Java system property as follows:
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %EXTRA_JAVA_PROPERTIES% set JAVA_PROPERTIES=%JAVA_PROPERTIES% -Didstore.identityAttribute=<name of the GUID attribute used by the identity store>
When you integrate with EPM System Release 184.108.40.206 or later, add the Java system property as follows:
set JAVA_PROPERTIES=%JAVA_PROPERTIES% %EXTRA_JAVA_PROPERTIES% set JAVA_PROPERTIES=%JAVA_PROPERTIES% -Doracle.epm.css.identity.type=fusion
Restart the Oracle WebLogic Server Administration Server and Managed Servers.
After restarting the Managed Servers, confirm that the Java system property has been applied by reviewing the standard out file (typically bi_server1.out or the console) and looking for the Java system property that you have added.
When these steps are complete, you can select SSO in the data source connection pool in the Oracle BI Repository to designate an SSO connection. In the case of Workspace integration, you can continue to configure Oracle Business Intelligence for SSO using the Hyperion SSO token.
However after following these steps and running a report in OBIEE based off Essbase gave the following error : (Note that Shared Services and OBIEE were using the same OID for authentication. The OID users were provisioned in Shared Services prior to testing this setup.
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A
general error has occurred. [nQSError: 43113] Message returned from OBIS.
[nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Login fails due to invalid login credentials (HY000)
When admin/password was used in the Connection Pool for essbase in rpd and unchecked SSO in connection pool settings, then the report ran fine
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