Click Lock Edit from the Change Center menu. Click Clone. Click OK. Click the newly created server WLS_OAM3. Click Save.

Managing Enterprise Deployments 20-25 2. Reconfigure the Oracle HTTP Server module with the new Managed Server. Follow the steps in Section 8.4, Configuring ODSM to work with the Oracle Web Tier. for the instructions to complete this task. Add the newly added Managed Server host name and port to the list WebLogicCluster Parameter.

20.3.2.2.3 Scaling Out Oracle Access Manager 11g Scale out is very similar to scale up but

first requires the software to be installed on the new node. Use the existing installations in shared storage for creating the new Managed Servers. You do not need to install WebLogic Server or Identity Management binaries in a new location but you do need to run pack and unpack to bootstrap the domain configuration in the new node. 1. On the new node, mount the existing Middleware home, which should include the SOA installation and the domain directory, and ensure that the new node has access to this directory, just like the rest of the nodes in the domain. 2. To update the Middleware home list, create or edit, if another WebLogic installation exists in the node the MW_HOMEbeabeahomelist file and add ORACLE_BASE productfmw to it. 3. Log in to the Oracle WebLogic Server Administration Console at http:admin.mycompany.comconsole. 4. From the Domain Structure window of the Oracle WebLogic Server Administration Console, expand the Environment node and then Servers. The Summary of Servers page appears.

5. Click Lock Edit from the Change Center menu.

6. Select an existing server on the host you want to extend, for example: WLS_OAM1.

7. Click Clone.

8. Enter the following information: ■ Server Name : A new name for the server, for example: WLS_OAM3. ■ Server Listen Address : The name of the host on which the Managed Server runs. ■ Server Listen Port : The port the new Managed Server uses. This port must be unique within the host.

9. Click OK.

10. Click the newly created server WLS_OAM3.

11. Set the SSL listen port. This should be unique on the host that the Managed Server runs on.

12. Click Save.

13. Disable host name verification for the new Managed Server. Before starting and verifying the WLS_OAM3 Managed Server, you must disable host name verification. You can re-enable it after you have configured server certificates for Note: If you are using shared storage, allow the new host access to that shared storage area. 20-26 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management the communication between the Oracle WebLogic Administration Server and the Node Manager in IDMHOSTn. If the source server from which the new one was cloned had already disabled host name verification, these steps are not required, as the host name verification settings was propagated to the cloned server. To disable host name verification, proceed as follows: a. In Oracle Enterprise Manager Fusion Middleware Control, select Oracle WebLogic Server Administration Console.

b. Expand the Environment node in the Domain Structure pane.

c. Click Servers. The Summary of Servers page appears.

d. Select WLS_OAM3 in the Names column of the table. The Settings page for

server appears.

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

14. Click Activate Configuration from the Change Center menu.

15. Restart the WebLogic Administration Server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 16. Pack the domain on IDMHOST1 using the command: pack.sh -domain=ORACLE_BASEadminIDMDomainaserverIDMDomain -template =tmpIDMDomain.jar -template_name=OAM Domain -managed=true The pack.sh script is located in MW_HOMEoracle_commoncommonbin. 17. Unpack the domain on the new host using the command: unpack.sh -domain=ORACLE_BASEadminIDMDomainmserverIDMDomain -template=tmpIDMDomain.jar -app_dir=ORACLE_ BASEadminIDMDomainmserverapplications The unpack.sh script is located in MW_HOMEoracle_commoncommonbin. 18. Start Node Manager and update the property file. a. Start and stop Node Manager as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. b. Run the script setNMProps.sh, which is located in ORACLE_COMMON_ HOME commonbin, to update the node manager properties file, for example: cd ORACLE_COMMON_HOMEcommonbin .setNMProps.sh c. Start Node Manager once again as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. Register the new Managed Server with Oracle Access Manager. The new Managed Server now must be configured as an Oracle Access Manager server. You do this from the Oracle OAM console, as follows: 1. Log in to the OAM console at http:admin.mycompany.comoamconsole as the oamadmin user.