Failing the Administration Server Back to IDMHOST1

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

This step checks that you can fail back the Administration Server, that is, stop it on IDMHOST2 and run it on IDMHOST1. To do this, migrate ADMINVHN back to IDMHOST1 node as follows: 1. On IDMHOST2, unmount the Administration server domain directory. For example: umount u01apporacleadminIDMDomainaserver 2. On IDMHOST1, mount the Administration server domain directory. For example: mount u01apporacleadminIDMDomainaserver 3. Ensure that the Administration Server is not running. If it is, stop it from the WebLogic console, or by running the command stopWeblogic.sh from DOMAIN_HOME bin. 4. Stop the Administration server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 5. Disable the ADMINVHN.mycompany.com virtual IP address on IDMHOST2 and run the following command as root on IDMHOST2: IDMHOST2 sbinifconfig x:y down where x:y is the current interface used by ADMINVHN.mycompany.com. 6. Run the following command on IDMHOST1: IDMHOST1 sbinifconfig interface:index 100.200.140.206 netmask 255.255.255.0 7. Update routing tables by using arping. Run the following command from IDMHOST1. Note: Ensure that the netmask and interface to be used match the available network configuration in IDMHOST1 Creating the WebLogic Server Domain for Identity Management 6-15 IDMHOST1 sbinarping -b -A -c 3 -I interface 100.200.140.206 8. If Node Manager is not already started on IDMHOST1, start it, as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 9. Start the Administration Server again on IDMHOST1. IDMHOST1 cd ORACLE_COMMON_HOMEcommonbin IDMHOST1 .wlst.sh Once in the wlst shell, execute wls:offlinenmConnectAdmin_User,Admin_Pasword, IDMHOST1,5556, IDMDomain,u01apporacleadminIDMDomainaserverIDMDomain wls:nmdomain_name nmStartAdminServer 10. Test that you can access the Oracle WebLogic Server Administration Console at http:ADMINVHN.mycompany.com:7001console. 11. Check that you can access and verify the status of components in the Oracle Enterprise Manager at http:ADMINVHN.mycompany.com:7001em.

6.15 Backing Up the WebLogic Domain