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

20-16 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management ■ Server Listen Port : The port the new Managed Server uses. 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 is 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 host name verification, these steps are not required, as the host name 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.

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.

You must now configure the new Managed Server now as an Oracle Access Manager server. You do this from the Oracle OAM console. Proceed as follows: 1. Log in to the OAM console at http:admin.mycompany.comoamconsole 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 is running on ■ Port : Listen port that was assigned when the Managed Server was created. ■ OAM Proxy Port : Port you want the Oracle Access Manager proxy to run on. This is unique for each host. ■ Proxy Server ID : AccessServerConfigProxy. ■ Mode : Open Managing Enterprise Deployments 20-17

6. Click Apply.

7. Click Coherence tab.

Set Local Port to a unique value on the host. 8. Click Apply. You can now start the Oracle Access Manager server. In order for the server to be used, however, you must inform all WebGates of its existence. You do this as follows: 1. Log in to the OAM console at http:admin.mycompany.comoamconsole as the oamadmin user.

2. Click the System Configuration tab

3. Expand Agents - OAM Agents - 10g Agents.

4. Double click the WebGate you want to change. 5. Add the new server to either the Primary or Secondary server list by clicking +. 6. Select the server name from the list.

7. Click Apply.

20.3.1.2.4 Scaling Up Oracle Identity Manager Adding Managed Servers to Existing Nodes In

this case, you already have a node that runs a Managed Server configured with SOA components. The node contains a Middleware home, an Oracle home SOA and a domain directory for existing Managed Servers. You can use the existing installations the Middleware home, and domain directories for creating new WLS_OIM and WLS_SOA servers. There is no need to install the Oracle Identity Manager and Oracle SOA Suite binaries in a new location, or to run pack and unpack. Follow these steps for scaling up the topology: 1. Using the Administration Console, clone either the WLS_OIM1 or the WLS_SOA1 into a new Managed Server. The source Managed Server to clone should be one that already exists on the node where you want to run the new Managed Server. To clone a Managed Server:

a. Select Environment - Servers from the Administration Console.