Deploying Oracle Access Manager on IDMHOST2 Updating Node Manager Properties File on IDMHOST2 Starting Oracle Access Manager Server on IDMHOST2

11-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

3. Click the Providers tab.

4. Click Lock and Edit from the Change Center.

5. In the list of authentication providers, select IAMSuiteAgent.

6. Click Delete.

7. Click Yes to confirm the deletion.

8. Click Activate Changes from the Change Center.

9. Restart WebLogic Adminisration Server and ALL running Managed Servers, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 10. Start the WebLogic Managed Server WLS_OAM1 as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

11.3.3 Propagating the Domain Changes to the Managed Server Domain Directory

To propagate the start scripts and classpath configuration from the Administration Servers domain directory to the Managed Server domain directory, proceed as follows: 1. Run the pack command on IDMHOST1 to create a template pack. Type the following commands: IDMHOST1 cd MW_HOMEoracle_commoncommonbin IDMHOST1 .pack.sh -managed=true -domain=ORACLE_ BASE adminIDMDomainaserverIDMDomain -template=MW_ HOMEtemplatesIDMDomain.jar -template_name=IDMDomain_Template

2. Run the unpack command on IDMHOST1 to unpack the propagated template to

the domain directory of the Managed Server. Type the following command: IDMHOST1 .unpack.sh -domain=ORACLE_BASEadminIDMDomainmserverIDMDomain -template=MW_HOMEtemplatesIDMDomain.jar -overwrite_domain=true -app_ dir=ORACLE_BASEadminIDMDomainmserverapplications

3. Restart Managed Server WLS_OAM1.

11.4 Configuring Oracle Access Manager on IDMHOST2

This section contains the following topics: ■ Section 11.4.1, Deploying Oracle Access Manager on IDMHOST2 ■ Section 11.4.2, Updating Node Manager Properties File on IDMHOST2 ■ Section 11.4.3, Starting Oracle Access Manager Server on IDMHOST2

11.4.1 Deploying Oracle Access Manager on IDMHOST2

Once the configuration has succeeded on IDMHOST1, you can propagate the configuration to IDMHOST2. You do this by packing the domain on IDMHOST1, using the pack script, and unpacking it on IDMHOST2 using the unpack script. Both scripts reside in MW_HOMEoracle_commoncommonbin. In Step 1 of Section 11.3.3, Propagating the Domain Changes to the Managed Server Domain Directory, you created a file called IDMDomain.jar in the MW_ HOME templates directory. Copy this file to IDMHOST2. Unpack the file on IDMHOST2 by using the unpack utility: 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