Click the SSL tab. Click Advanced. Set Hostname Verification to None. Click Save.

20-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

10. Click Activate configuration from the Change Center menu.

Register the new Managed Server with Oracle Access Manager. You now must 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 runs 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 the host ■ Proxy Server ID : AccessServerConfigProxy ■ Mode : Set to Open or Simple, depending on the mode your existing Oracle Access Manager servers are operating in.

6. Click Coherence tab.

Set Local Port to a unique value on the host. 7. Click Apply. 8. Restart the WebLogic Administration Server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. Add the newly created Oracle Access Manager server to all WebGate Profiles that might be using it, such as Webgate_IDM and IAMSuiteAgent For example, to add the Oracle Access Manager server to Webgate_IDM, access the OAM console at http:admin.mycompany.comoamconsole, then proceed as follows: 1. Log in as the Oracle Access Manager Admin User you created in Section 10.4.2, Creating Users and Groups for Oracle Access Manager.

2. Click the System Configuration tab.

3. Expand Access Manager Settings - SSO Agents - OAM Agents.

4. Click the open folder icon, then click Search.

You should see the WebGate agent Webgate_IDM. 5. Click the agent Webgate_IDM. 6. Select Edit from the Actions menu. Managing Enterprise Deployments 20-15 7. Click + in the Primary Server list or the Secondary Server list if this is a secondary server.

8. Select the newly created managed server from the Server drop down list.

9. Set Max Connections to 4.

10. Click Apply.

Repeat Steps 5 through 10 for IAMSuiteAgent and all other WebGates that might be in use. Update the Web Tier. Once the new Managed Server has been created and started, the web tier starts to direct requests to it. Best practice, however, is to inform the web server that the new Managed Server has been created. You do this by updating the file OAM.conf on each of the web tiers. This file resides in the directory: ORACLE_INSTANCEconfigOHScomponent namemoduleconf. Add the new server to the WebLogicCluster directive in the file, for example, change: Location oam SetHandler weblogic-handler WebLogicCluster idmhost1.mycompany.com:14100,idmhost2.mycompany.com:14100 Location to: Location oam SetHandler weblogic-handler WebLogicCluster idmhost1.mycompany.com:14100,idmhost2.mycompany.com:14100,idmhost1.mycompany.com:1 4101 Location Save the file and restart the Oracle HTTP server, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. You can now start the new Managed Server, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components.

20.3.1.2.3 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:admin.mycompany.comconsole. 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 runs. 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