Prerequisites Configuring Oracle HTTP Servers to Display Login Page Configuring Oracle HTTP Servers to Access Oracle Access Manager Console

Extending the Domain with Oracle Access Manager 11g 11-7 .unpack.sh -domain=ORACLE_BASEadminIDMDomainmserverIDMDomain -template=MW_ HOME templatesIDMDomain.jar -overwrite_domain=true -app_dir=ORACLE_ BASE adminIDMDomainmserverapplications

11.4.2 Updating Node Manager Properties File on IDMHOST2

If the Node Manager is not already started on IDMHOST2, perform the following steps to start it: 1. Start the Node Manager on IDMHOST2 to create the nodemanager.properties file by using the startNodemanager.sh script located under the MW_ HOME wlserver_10.3serverbin directory. 2. Before you can start the Managed Servers by using the console, node manager requires that the property StartScriptEnabled is set to true. You set it by running the setNMProps.sh script located under the MW_HOMEoracle_ commoncommonbin directory. prompt MW_HOMEoracle_commoncommonbin prompt .setNMProps.sh 3. Stop and Start the Node Manager as described in Section 20.1, Starting and Stopping Oracle Identity Management Components so that the properties take effect.

11.4.3 Starting Oracle Access Manager Server on IDMHOST2

Start Oracle Access Manager on IDMHOST2 by following the start procedures in Section 20.1, Starting and Stopping Oracle Identity Management Components for: ■ Node Manager if it is not already started ■ WebLogic Managed Server WLS_OAM2

11.5 Configuring Oracle Access Manager to work with the Oracle Web Tier

This section describes how to configure Oracle Access Manager to work with the Oracle Web Tier. This section contains the following topics: ■ Section 11.5.1, Prerequisites ■ Section 11.5.2, Configuring Oracle HTTP Servers to Display Login Page ■ Section 11.5.3, Configuring Oracle HTTP Servers to Access Oracle Access Manager Console ■ Section 11.5.4, Validating Accessibility

11.5.1 Prerequisites

Before proceeding, ensure that the following tasks have been performed: 1. Configure Oracle Web Tier on WEBHOST1 and WEBHOST2 as described in Section 5.1, Configuring the Oracle Web Tier. 2. Configure Oracle Access Manager on IDMHOST1 and IDMHOST2 as described in Section 11.3, Configuring Oracle Access Manager on IDMHOST1 and Section 11.4, Configuring Oracle Access Manager on IDMHOST2. 11-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 3. Configure the load balancer with a virtual host name sso.mycompany.com routing traffic to the webservers on WEBHOST1 and WEBHOST2 as described in Section 2.2.2, Configuring Virtual Server Names and Ports on the Load Balancer. 4. Configure the load balancer with a virtual host name admin.mycompany.com routing traffic to webservers WEBHOST1 and WEBHOST2 Section 2.2.2, Configuring Virtual Server Names and Ports on the Load Balancer.

11.5.2 Configuring Oracle HTTP Servers to Display Login Page

On each of the web servers on WEBHOST1 and WEBHOST2 create a file called oam.conf in the directory ORACLE_INSTANCEconfigOHScomponentmoduleconf. This file must contain the following information: Location oam SetHandler weblogic-handler WebLogicCluster idmhost1.mycompany.com:14100,idmhost2.mycompany.com:14100 Location

11.5.3 Configuring Oracle HTTP Servers to Access Oracle Access Manager Console

On each of the web servers on WEBHOST1 and WEBHOST2, a file called admin.conf was created in the directory ORACLE_ INSTANCE configOHScomponentmoduleconf. See Section 6.9, Configuring Oracle HTTP Server for the WebLogic Administration Server . Edit this file and add the following lines within the virtual host definition: Location oamconsole SetHandler weblogic-handler WebLogicHost ADMINVHN WebLogicPort 7001 Location After editing the file should look like: NameVirtualHost :80 VirtualHost :80 ServerName admin.mycompany.com:80 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit RewriteRule consolejspcommonlogout.jsp oamssologout.html [PT] RewriteRule emtargetauthemaslogout.jsp oamssologout.html [PT] Admin Server and EM Location console SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 Location Location consolehelp SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 Location Location em Extending the Domain with Oracle Access Manager 11g 11-9 SetHandler weblogic-handler WebLogicHost ADMINVHN WeblogicPort 7001 Location Location oamconsole SetHandler weblogic-handler WebLogicHost ADMINVHN WebLogicPort 7001 Location VirtualHost Restart the Oracle HTTP Server, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

11.5.4 Validating Accessibility