Starting the Administration Server on IDMHOST2 Validating Access to IDMHOST2 Through Oracle HTTP Server

Creating the WebLogic Server Domain for Identity Management 6-13 netsh interface ip delete address interface netmask In the following example, the IP address is disabled on the interface Local Area Connection: netsh interface ip delete address Local Area connection 100.200.140.206 b. Run the following command on IDMHOST2: netsh interface ip add address interface IP_Address netmask In the following example, the IP address is enabled on the interface Local Area Connection: netsh interface ip add address Local Area connection 100.200.140.206 255.255.255.0

6.14.2 Starting the Administration Server on IDMHOST2

Perform the following steps to start Node Manager on IDMHOST2: 1. On IDMHOST1, unmount the Administration Server domain directory. For example: umount u01apporacleadminIDMDomainaserver

2. On IDMHOST2, mount the Administration Server domain directory. For example:

mount u01apporacleadminIDMDomainaserver 3. Start Node Manager by using the following commands: IDMHOST2 cd ORACLE_BASEproductfmwwlserver_10.3serverbin IDMHOST2 .startNodeManager.sh 4. Stop Node Manager.

5. Run the setNMProps.sh script to set the StartScriptEnabled property to true

before starting Node Manager: cd MW_HOMEoracle_commoncommonbin .setNMProps.sh 6. Start the Node Manager as described in Section 20.1.5.3, Starting Node Manager for an Administration Server. 7. Start the Administration Server on IDMHOST2. DMHOST2 cd ORACLE_COMMON_HOMEcommonbin Note: Starting and stopping Node Manager at this point is only necessary the first time you run Node Manager. Starting and stopping it creates a property file from a predefined template. The next step adds properties to that property file. Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. 6-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management IDMHOST2 .wlst.sh Once in the wlst shell, execute the following commands: wls:offline nmConnectAdmin_User,Admin_Password, IDMHOST2,5556, IDMDomain,u01apporacleadminIDMDomainaserverIDMDomain wls:nmdomain_name nmStartAdminServer 8. Test that you can access the Administration Server on IDMHOST2 as follows: a. Ensure that you can access the Oracle WebLogic Server Administration Console at http:ADMINVHN.mycompany.com:7001console. b. Check that you can access and verify the status of components in the Oracle Enterprise Manager at http:ADMINVHN.mycompany.com:7001em.

6.14.3 Validating Access to IDMHOST2 Through Oracle HTTP Server

Perform the same steps as in Section 6.13, Validating Access Through Oracle HTTP Server. This is to check that you can access the Administration Server when it is running on IDMHOST2.

6.14.4 Failing the Administration Server Back to IDMHOST1