From the Domain Structure window of the Oracle WebLogic Server In the Change Center, click Lock Edit. Select an existing server on the host you wish to extend, for example: WLS_OAM1. Click Clone. Enter the following information: Click OK. Click on the ne

8-146 Oracle Fusion Middleware High Availability Guide Log in to the console using the url http:admin.us.oracle.comoamconsole, then follow these steps:

1. Click on the System Configuration tab.

2. Expand Servers in the navigator.

3. Double-click on the Managed Server whose port you wish to change.

4. Click on the Coherence tab.

5. Change the value of Local Port to the desired value.

6. Click Apply.

7. Restart the Administration Server and all the managed servers residing in the same cluster as the managed server that has been updated.

8.8.4.15 Scaling Up and Scaling Out the Oracle Access Manager Topology

This section describes how to scale up and scale out an Oracle Access Manager high availability topology. Perform a scale up operation to add a new Oracle 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 Access Manager managed server instance to a new node.

8.8.4.15.1 Scaling Up Oracle Access Manager Scale up OAM as follows:

Log in to the Oracle WebLogic Server Administration Console at http:oamhost1.mycompany.com:7001console.

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. In the Change Center, click Lock Edit.

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

4. Click Clone.

5. 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 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 on the newly created server WLS_OAM3

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_OAM3 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 OAMHOSTn. Configuring High Availability for Identity Management Components 8-147 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 Oracle Enterprise Manager Fusion Middleware Control, select Oracle

WebLogic Server Administration Console .

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

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.

11. Click Activate configuration from the Change Center menu.

Register the new managed server with OAM. You now need to configure the new managed server now as an OAM server. You do this from the Oracle OAM console. Proceed as follows: 1. Log in to the OAM console at http:oamhost1.mycompany.com:7001oamconsole as the oamadmin user.

2. Click the System Configuration tab.

3. Click Server Instances.

4. Select Create from the Actions menu.

5. Enter the following information: ■ Server Name : WLS_OAM3 ■ Host : Host that the server will run on ■ Port : Listen port that was assigned when the managed server was created ■ OAM Proxy Port : Port you want the OAM proxy to run on. This is unique for the host ■ Proxy Server ID : AccessServerConfigProxy ■ Mode : Open

6. Click Coherence tab.

Set Local Port to a unique value on the host. Click Apply.

7. Click Apply.

You can now start the Access server. To use the Access server, you must inform any Webgates of its existence. You do that as follows: 1. Log in to the OAM console at http:oamhost1.mycompany.com:7001oamconsole as the oamadmin user.

2. Click the System Configuration tab.