In the Oracle Fusion Middleware Enterprise Manager Console, select Oracle Expand the Environment node in the Domain Structure pane. Click Servers. The Summary of Servers page appears. Select WLS_OAAM3 in the Names column of the table. The Settings page fo

8-228 Oracle Fusion Middleware High Availability Guide Also, log into the Oracle Adaptive Access Manager server at http:oaam.mycompany.com:7777oaam_server using the oaamadmin account and the password test.

8.12.3.14 Scaling Up and Scaling Out the Oracle Adaptive Access Manager Topology

This section describes how to scale up and scale out an Oracle Adaptive Access Manager high availability topology. Perform a scale up operation to add a new Oracle Adaptive Access Manager managed server instance is added to a node already running one or more server instances. Perform a scale out operation to add a new Oracle Adaptive Access Manager managed server instance to a new node.

8.12.3.14.1 Scaling Up Oracle Adaptive Access Manager To scale up OAAM, use the same

procedure for both the OAAM server and the OAAM Administration Server. Log in to the Oracle WebLogic Server console at: http:oaamhost1.mycompany.com:7001console. Then proceed as follows: 1. 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.

2. Click Lock Edit from the Change Center menu.

3. Select an existing server on the host that you want to extend, for example: WLS_ OAAM1 or WLS_OAAM_ADMIN1.

4. Click Clone.

5. Enter the following information: ■ Server Name : A new name for the server, for example: WLS_OAAM3. ■ Server Listen Address : The name of the host on which the managed server will run. ■ Server Listen Port : The port the new managed server will use. This port must be unique within the host.

6. Click OK.

7. Click the newly-created server WLS_OAAM3.

8. Set the SSL listen port. This should be unique on the host that the managed server will be running on.

9. Click Save.

10. Disable host name verification for the new managed server. Before starting and verifying the WLS_OAAM3 managed server, you must disable host name verification. You can re-enable it after you have configured server certificates for the communication between the Oracle WebLogic Administration Server and the Node Manager in OAAMHOSTn. If the source server from which the new one was cloned had already disabled hostname verification, these steps are not required, as the hostname verification settings were propagated to the cloned server. To disable host name verification:

a. In the Oracle Fusion Middleware Enterprise Manager Console, 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.

Configuring High Availability for Identity Management Components 8-229

d. Select WLS_OAAM3 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.

11. Click Activate configuration from the Change Center menu.

8.12.3.14.2 Scaling Out Oracle Adaptive Access Manager Scale out is very similar to scale

up, but first requires the software to be installed on the new node. Proceed as follows: 1. Install Oracle WebLogic Server on the new host as described in Section 8.12.3.3, Installing Oracle WebLogic Server. 2. Install Oracle Fusion Middleware Identity Management components on the new host as described in Section 8.12.3.4, Install and Configure the Oracle Adaptive Access Manager Application Tier. 3. Log in to the WebLogic console at http:oaamhost1.mycompany.com:7001console. 4. From the Domain Structure pane 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_OAAM1 or WLS_OAAM_ADMIN1.

7. Click Clone.

8. Enter the following information: ■ Server Name : A new name for the server, for example: WLS_OAAM3 ■ Server Listen Address : The name of the host on which the managed server will run. ■ Server Listen Port : The port the new managed server will use. This port must be unique within the host.

9. Click OK.

10. Click the newly-created server WLS_OAAM3.

11. Set the SSL listen port. This should be unique on the host that the managed server will be running on.

12. Click Save.

13. Disable host name verification for the new managed server. Before starting and verifying the WLS_OAAM3 managed server, you must disable host name verification. You can re-enable it after you have configured server certificates for the communication between the Oracle WebLogic Administration Server and the Node Manager in OAAMHOSTn. If the source server from which the new one was cloned had already disabled hostname verification, these steps are not required, as the hostname verification settings were propagated to the cloned server. To disable host name verification: 8-230 Oracle Fusion Middleware High Availability Guide

a. In the Oracle Fusion Middleware Enterprise Manager Console, select Oracle