Failing over the Administration Server to IDMHOST2

Creating the WebLogic Server Domain for Identity Management 6-11

6.13 Validating Access Through Oracle HTTP Server

Verify that the server status is reported as Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported such as Admin or Failed, check the server output log files for errors. See Section 20.6, Troubleshooting for possible causes. Validate Administration Console and Oracle Enterprise Manager Fusion Middleware Control through Oracle HTTP Server using the following URLs: ■ http:admin.mycompany.comconsole ■ http:admin.mycompany.comem For information on configuring system access through the load balancer, see Section 2.2.1, Load Balancers.

6.14 Manually Failing Over the WebLogic Administration Server

This section discusses how to fail over the Administration Server to IDMHOST2 and how to fail it back to IDMHOST1. This section contains the following topics: ■ Section 6.14.1, Failing over the Administration Server to IDMHOST2 ■ Section 6.14.2, Starting the Administration Server on IDMHOST2 ■ Section 6.14.3, Validating Access to IDMHOST2 Through Oracle HTTP Server ■ Section 6.14.4, Failing the Administration Server Back to IDMHOST1

6.14.1 Failing over the Administration Server to IDMHOST2

If a node fails, you can fail over the Administration Server to another node. This section describes how to fail over the Administration Server from IDMHOST1 to IDMHOST2. Assumptions: ■ The Administration Server is configured to listen on ADMINVHN.mycompany.com, and not on ANY address. See step 10 in Section 6.2, Running the Configuration Wizard on IDMHOST1 to Create a Domain. ■ The Administration Server is failed over from IDMHOST1 to IDMHOST2, and the two nodes have these IP addresses: – IDMHOST1: 100.200.140.165 – IDMHOST2: 100.200.140.205 – ADMINVIP: 100.200.140.206 Note: After registering the Oracle HTTP Server as described in Section 6.10, Registering Oracle HTTP Server with WebLogic Server, the Oracle HTTP Server should appear as a manageable target in Oracle Enterprise Manager Fusion Middleware Control. To verify this, log in to Fusion Middleware Control. The WebTier item in the navigation tree should show that Oracle HTTP Server has been registered. 6-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management This is the Virtual IP address where the Administration Server is running, assigned to interface:index for example, eth1:2, available in IDMHOST1 and IDMHOST2. ■ The domain directory where the Administration Server is running in IDMHOST1 is on a shared storage and is mounted also from IDMHOST2. ■ Oracle WebLogic Server and Oracle Fusion Middleware Components have been installed inIDMHOST2 as described in previous chapters. That is, the same path for IDM_ORACLE_HOME and MW_HOME that exists in IDMHOST1 is available in IDMHOST2. The following procedure shows how to fail over the Administration Server to a different node, IDMHOST2. Linux 1. Stop the Administration Server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 2. Migrate the IP address to the second node. a. Run the following command as root on IDMHOST1 where x:y is the current interface used by ADMINVHN.mycompany.com: IDMHOST1 sbinifconfig x:y down For example: IDMHOST1 sbinifconfig eth0:1 down b. Run the following command on IDMHOST2: IDMHOST2 sbinifconfig interface:index IP_Address netmask netmask For example: sbinifconfig eth0:1 10.0.0.1 netmask 255.255.255.0 3. Update routing tables by using arping, for example: IDMHOST2 sbinarping -b -A -c 3 -I eth0 10.0.0.1 Windows 1. Stop the Administration Server as described in Section 20.1, Starting and Stopping Oracle Identity Management Components. 2. Migrate the IP address to the second node. a. Run the following command as root on IDMHOST1 Note: NM in IDMHOST2 does not control the domain at this point, since unpacknmEnroll has not been run yet on IDMHOST2. But for the purpose of AdminServer failover and control of the AdminServer itself, Node Manager is fully functional Note: Ensure that the netmask and interface to be used match the available network configuration in IDMHOST2. 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