Assumptions and Procedure Manually Failing Over the Administration Server to SOAHOST2

5-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

5.11 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 12.8, Troubleshooting for possible causes. Validate Administration Console and Enterprise Manager through both Oracle HTTP Server instances using the following URLs: ■ http:WEBHOST1:7777console ■ http:WEBHOST2:7777console ■ http:WEBHOST1:7777em ■ http:WEBHOST2:7777em ■ http:admin.mycompany.comconsole ■ http:admin.mycompany.comem For information on configuring system access through the load balancer, see Section 2.2.2, Load Balancers.

5.12 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: ■ Section 5.12.1, Assumptions and Procedure ■ Section 5.12.2, Validating Access to SOAHOST2 Through Oracle HTTP Server ■ Section 5.12.3, Failing the Administration Server Back to SOAHOST1

5.12.1 Assumptions and Procedure

Please note the following assumptions: ■ The Administration Server is configured to listen on ADMINVHN, and not on ANY address. See step 12 in Section 5.2, Running the Configuration Wizard on SOAHOST1 to Create a Domain . ■ The Administration Server is failed over from SOAHOST1 to SOAHOST2, and the two nodes have these IP addresses: – SOAHOST1: 100.200.140.165 – SOAHOST2: 100.200.140.205 – ADMINVHN: 100.200.140.206. This is the VIP where the Administration Server is running, assigned to ethX:Y, available in SOAHOST1 and SOAHOST2. Note: After setting the frontend URL to the LBR address, the access to the console through the WEBHOSTn addresses will be redirected by the console to the frontend URL, thus validating the correct configuration of both Oracle HTTP Server and the LBR device. Creating a Domain with Administration Server 5-11 ■ The domain directory where the administration server is running in SOAHOST1 is on a shared storage and is mounted also from SOAHOST2. ■ Oracle WebLogic Server and Oracle FMW components have been installed in SOAHOST2 as described in Chapter 3, Installing the Software that is, the same paths for ORACLE_HOME and MW_HOME that exist on SOAHOST1 are also available on SOAHOST2. Procedure The following procedure shows how to fail over the Administration Server to a different node SOAHOST2: 1. Stop the Administration Server if it is running. 2. Migrate the IP address 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 100.200.140.206 netmask 255.255.255.0 c. Update the routing tables using arping, for example: SOAHOST2 sbinarping -b -A -c 3 -I eth0 100.200.140.206 3. Start Node Manager in SOAHOST2 as described in Section 5.4, Starting Node Manager on SOAHOST1. 4. Start the Administration Server on SOAHOST2 as described in Section 5.5, 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. Note: Node Manager in SOAHOST2 will not control the domain domain_name at this point, since unpacknmEnroll has not been run yet on SOAHOST2. However, for the purpose of AdminServer failover and control of the administration server itself, Node Manager will be fully functional. Later failovers after unpack has been run in SOAHOST2 will correctly have Node Manager controlling the domain. Note: Make sure that the netmask and interface to be used match the available network configuration in SOAHOST2. 5-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

5.12.2 Validating Access to SOAHOST2 Through Oracle HTTP Server