All SAP systems within the SAP landscape must be set up for SSO with the SAP logon ticket. User names must be normalized across the SAP landscape so that a user name in one SAP system refers to the same user across all SAP systems. See SAP documentation for more information.
Copy or download the SAP JCo binaries or shared libraries into EPM_ORACLE_HOME/common/SAP/bin directory.
JCo binaries and shared libraries are available in your SAP distribution. Registered SAP users can download them from the SAP web site https://service.sap.com/connectors.
Copy or download the SAP JCo archives (JAR files) and libraries into EPM_ORACLE_HOME/common/SAP/lib directory.
JCo archives and libraries are available in your SAP distribution. Registered SAP users can download them from the SAP web site https://service.sap.com/connectors.
The following libraries are required to verify that the SAP SSO ticket provided to EPM System products. This step is required only if EPM System products are plugged into SAP Enterprise Portal.
com.sap.security.core.jar
com.sap.security.api.jar
sapjco.jar
sap.logging.jar
iaik_jce.jar
iaik_jce_export.jar (if using the export version of the IAIK-JCE libraries)
Expand the contents of each SAP JAR file by running explodejar.sh or explodejar.bat, available in EPM_ORACLE_HOME/common/SAP/lib directory.
Install the SAP Digital Certificate (SAP X509 certificate, SAP.keystore) in a convenient location.
Using Shared Services Console, configure SAP provider as an External user directory. See “Configuring SAP R3 Native Directory” in the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.
Using Shared Services Console, provision SAP users and groups to provide them access to EPM System products. See “Provisioning Users and Groups” in the Oracle Hyperion Enterprise Performance Management System User and Role Security Guide.