Expand the Environment node in the Domain Structure pane. Click Servers. The Summary of Servers page appears. Select WLS_OAM3 in the Names column of the table. The Settings page for Click the SSL tab. Click Advanced. Set Hostname Verification to None. Cli

Configuring High Availability for Identity Management Components 8-149 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. Pack the domain on OAMHOST1 using the command: pack.sh -domain=ORACLE_BASEadminIDM_DomainaserverIDM_Domain -template =tmpidm_domain.jar -template_name=OAM Domain -managed=true The pack.sh script is located in MW_HOMEoracle_commoncommonbin. 16. Unpack the domain on the new host using the command: unpack.sh -domain=ORACLE_BASEadminIDM_DomainmserverIDM_Domain -template=tmpidm_domain.jar -template_name=OAM Domain -app_dir=ORACLE_ BASEadminIDM_Domainmserverapplications The unpack.sh script is located in MW_HOMEoracle_commoncommonbin. 17. Before you can start managed servers from the console, you must create a node manager properties file on OAMHOST3. You do this by running the script setNMProps.sh, which is located in MW_HOMEoracle_commoncommonbin. Type: MW_HOME oracle_commoncommonbinsetNMProps.sh Register the new managed server with OAM. The new managed server now needs to be configured as an OAM server. You do this from the Oracle OAM console, 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 be running on, OAMHOST3. ■ 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 8-150 Oracle Fusion Middleware High Availability Guide ■ Mode : Open

6. Click Apply.

You can now start the Access Server. In order for the server to be used, however, 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.

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 the Add [+] icon. 6. Select the server name from the list.

7. Click Apply.

Update the Web Tier. Now that the new managed server has been created and started, the web tier will start 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_admin SetHandler weblogic-handler WebLogicCluster OAMhost1.mycompany.com:14200,OAMhost2.mycompany.com:14200 Location to: Location OAM_admin SetHandler weblogic-handler WebLogicCluster OAMhost1.mycompany.com:14200,OAMhost2.mycompany.com:14200,OAMhsot3.mycompany.com:1 4300 Location

8.9 Oracle Identity Manager High Availability