Click Lock Edit. Navigate to SecurityRealms, then the default realm name, and then Providers. Click OK.

Integration with Oracle Identity Management 11-31

11.3.5.1 Backing Up Configuration Files

To be safe, first back up the relevant configuration files: ORACLE_BASE admindomain_nameaserverdomain_nameconfigconfig.xml ORACLE_BASE admindomain_nameaserverdomain_nameconfigfmwconfigjps-config.xml ORACLE_BASE admindomain_nameaserverdomain_nameconfigfwmconfig system-jazn-data.xml In addition, back up the boot.properties file for the Administration Server.

11.3.5.2 Setting Up the OAM ID Asserter

Perform these steps to set up the OAM ID Asserter: 1. Log in to Weblogic Console, if not already logged in.

2. Click Lock Edit.

3. Navigate to SecurityRealms, then the default realm name, and then Providers.

4. Click New and select OAM Identity Asserter from the dropdown menu.

5. Name the asserter for example, OAM ID Asserter and click OK.

6. Click the newly added asserter to see the configuration screen for OAM Identity Asserter. 7. Set the control flag to ’REQUIRED’.

8. Select both the ObSSOCookie and OAM_REMOTE_USER options under active

types. 9. Save the settings. Finally, log in to the WLST console as an administrator and run the following command: addOAMSSOProviderloginuri={app.context}adfAuthentication,logouturi=oams sologout.html

11.3.5.3 Setting the Order of Providers

Perform these steps to set the order of the providers: 1. Log in to Weblogic Console, if not already logged in.

2. Click Lock Edit.

3. Navigate to SecurityRealms, then the default realm name, and then Providers.

4. Reorder the OAM Identity Asserter, OIDOVD Authenticator, and Default Authenticator by ensuring that the control flag for each authenticator is set as follows: ■ OAM Identity Asserter: REQUIRED ■ OID LDAP Authenticator or OVD LDAP Authenticator: SUFFICIENT ■ Default Authenticator: SUFFICIENT

5. Click OK.

11-32 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

11.4 Validating Access Through Oracle HTTP Server and SSO

Validate single sign-on through both Oracle HTTP Server instances using the following URLs: ■ http:WEBHOST1:7777console ■ http:WEBHOST1:7777em ■ http:WEBHOST1:7777cs ■ http:WEBHOST1:7777imaging ■ http:WEBHOST2:7777console ■ http:WEBHOST2:7777em ■ http:WEBHOST2:7777cs ■ http:WEBHOST2:7777imaging Then validate single sign-on through the front-end using the SSO username and password: ■ http:admin.mycompany.comconsole ■ http:admin.mycompany.comem ■ http:ecm.mycompany.comcs ■ http:ecm.mycompany.comimaging

11.5 Backing Up the Installation

After you have verified that the extended domain is working, back up the installation. This is a quick backup for the express purpose of immediate restore in case of problems in the further steps. The backup destination is the local disk. This backup can be discarded once the enterprise deployment setup is complete. At that point, the regular deployment-specific backup and recovery process can be initiated. The Oracle Fusion Middleware Administrators Guide provides further details. For information on describing the Oracle HTTP Server data that must be backed up and restored, refer to the Backup and Recovery Recommendations for Oracle HTTP Server section in this guide. For information on how to recover components, see Recovery of Components and Recovery After Loss of Component sections in the guide. For recommendations specific to recovering from the loss of a host, see the Recovering Oracle HTTP Server to a Different Host in the guide. Also refer to the Oracle Database Backup and Recovery Users Guide for information on database backup. Perform these steps to back up the installation at this point: 1. Back up the web tier: a. Shut down the instance using opmnctl. ORACLE_BASEadmininstance_namebinopmnctl stopall b. Back up the Middleware Home on the web tier using the following command as root: tar -cvpf BACKUP_LOCATIONweb.tar MW_HOME c. Back up the Instance Home on the web tier using the following command as root: tar -cvpf BACKUP_LOCATIONweb_instance.tar ORACLE_INSTANCE