Click Servers. The Summary of Servers page appears. Select WLS_SOAn in the Names column of the table. Click the SSL tab. Click Advanced. Set Hostname Verification to None. Click Save. In the left pane, expand Environment and select Servers. Click the Migr

Managing Enterprise Deployments 20-35

c. Navigate to Identity and Access, and then oim.

d. Right-click oim and navigate to System MBean Browser.

e. Under Application Defined MBeans, navigate to oracle.iam, Application:oim , XMLConfig, Config, XMLConfig.SOAConfig, and then SOAConfig .

f. Update the value for the Rmiurl attribute with the host and port of the new

SOA server. Click Apply to save the changes. g. The Rmiurl attribute is used for accessing SOA EJBs deployed on SOA Managed Servers. This is the application server URL. For a clustered deployment of Oracle Identity Manager, it is a comma-delimited list of all the SOA Managed Server URLs. The following are example values for this attribute: t3:oimhost1.mycompany.com:8001 oimhost2.mycompany.com:8001 oimhost3.mycompany.com:8001 15. Configure TX persistent store for the new server. This should be a location visible from other nodes as indicated in the recommendations about shared storage. From the Administration Console, select Server_name Services tab. Under Default Store , in Directory, enter the path to the folder where you want the default persistent store to store its data files. 16. Disable host name verification for the new Managed Server. Before starting and verifying the WLS_SOAn 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 SOAHOSTn. If the source server from which the new one has been cloned had already disabled host name verification, these steps are not required the host name verification setting is propagated to the cloned server. To disable host name verification:

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

b. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server

Administration Console .

c. Click Servers. The Summary of Servers page appears.

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

17. Click Activate Configuration from the Change Center menu.

18. Start the Node Manager on the new node. To start the Node Manager, use the installation in shared storage from the existing nodes, and start Node Manager by passing the host name of the new node as a parameter as follows: SOAHOSTN WL_HOMEserverbinstartNodeManager new_node_ip 20-36 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 19. Start and test the new Managed Server from the Oracle WebLogic Server Administration Console: 1. Shut down all the existing Managed Servers in the cluster. 2. Ensure that the newly created Managed Server, WLS_SOAn, is running. 3. Access the application on the newly created Managed Server http:vip:portsoa-infra. The application should be functional. 20. Configure server migration for the new Managed Server. Configure server migration following these steps: a. Log in to the Administration Console.

b. In the left pane, expand Environment and select Servers.

c. Select the server represented as hyperlink for which you want to configure migration from the Names column of the table. The Setting page for that server appears.

d. Click the Migration tab.

e. In the Available field, in the Migration Configuration section, select the

machines to which to enable migration and click the right arrow.

f. Select the Automatic Server Migration Enabled option. This enables the Node

Manager to start a failed server on the target node automatically.

g. Click Save.