Manually Failing Over the Administration Server to SOAHOST2

Creating a Domain 4-21

4.22 Manually Failing Over the Administration Server to SOAHOST2

In case a node fails, you can fail over the Administration Server to another node. This section describes how to fail over the Administration Server from SOAHOST1 to SOAHOST2. Assumptions: ■ The Administration Server is configured to listen on ADMINVHN, and not on ANY address. See step 14 in Section 4.4, Running the Configuration Wizard on SOAHOST1 to Create a Domain . ■ These procedures assume that the two nodes use two individual domain directories, and that the directories reside in local storage or in shared storage in different volumes. ■ The Administration Server is failed over from SOAHOST1 to SOAHOST2, and the two nodes have these IPs: – SOAHOST1: 100.200.140.165 – SOAHOST2: 100.200.140.205 – VIPHOST1: 100.200.140.206. This is the VIP where the Administration Server is running, assigned to ethX:Y, available in SOAHOST1 and SOAHOST2. ■ The domain directory where the Administration Server is running in SOAHOST1 is on a shared storage and is mounted also from SOAHOST2. The following procedure shows how to fail over the Administration Server to a different node SOAHOST2, but the Administration Server will still use the same WebLogic Server machine which is a logical machine, not a physical machine. 1. Stop the Administration Server. 2. Migrate IP to the second node. a. Run the following command as root on SOAHOST1 where X:Y is the current interface used by ADMINVHN: SOAHOST1 sbinifconfig ethX:Y down b. Run the following command on SOAHOST2: SOAHOST2 sbinifconfig interface:index IP_Address netmask netmask For example: sbinifconfig eth0:1 10.0.0.1 netmask 255.255.255.0 Note: After the registering Oracle HTTP Server as described in Section 4.19, Registering Oracle HTTP Server With WebLogic Server, the Oracle HTTP Server should appear as a manageable target in the Oracle Enterprise Manager Console. To verify this, log into the Enterprise Manager Console. The WebTier item in the navigation tree should show that Oracle HTTP Server has been registered. Note: Ensure that the netmask and interface to be used to match the available network configuration in SOAHOST2. 4-22 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 3. Update routing tables through arping, for example: SOAHOST2 sbinarping -b -A -c 3 -I eth0 10.0.0.1 4. Start the Administration Server on SOAHOST2 using the procedure in Section 4.7, Starting the Administration Server on SOAHOST1. . 5. Test that you can access the Administration Server on SOAHOST2 as follows: a. Ensure that you can access the Oracle WebLogic Server Administration Console at http:ADMINVHN:7001console. b. Check that you can access and verify the status of components in the Oracle Enterprise Manager at http:ADMINVHN:7001em.

4.23 Validating Access to SOAHOST2 Through Oracle HTTP Server