Administration Server Topology 2 Transforming Oracle Fusion Middleware Infrastructure Components

Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-11 f. Start the Administration Server process. DOMAIN_HOME binstartWebLogic.sh Where DOMAIN_HOME is the location of your domain directory. g. Validate access to both the Administration Server and Enterprise Manager console.

12.2.2.2 Administration Server Topology 2

Figure 12–2 illustrates the second supported Administration Server topology for Oracle Cold Failover Cluster. Figure 12–2 Administration Server Cold Failover Cluster Topology 2 In Figure 12–2 , the Administration Server runs on a two-node hardware cluster: Node 1 and Node 2. The Administration Server is listening on the Virtual IP or hostname. The domain directory used by the Administration Server is on a shared disk. This is mandatory. This shared disk is mounted on Node 1 or Node 2 at any given point. The Middleware Homes, which contain the software, WebLogic Home and the Oracle Home are not necessarily on a shared disk. They can be on the local disk as well. The Administration Server uses the Middleware Home on Node1 for the software when it is running on Node1 and it uses the Middleware Home on Node2 when it is running on Node2. These two Middleware Home must be maintained to be the same in terms of deployed products, Oracle Homes, and patches. In both cases, it uses the configuration available in the shared Domain DirectoryDomain Home. Since this is shared, it ensures that the same configuration is used before and after failover. This shared domain directory may also have other Managed Servers running. It may also be used exclusively for the Administration Server. If the domain directory is shared with other managed servers, appropriate consideration must be made for their failover when the Administration Server fails over. Some of these considerations are: 1. If the shared storage can be mounted as readwrite on multiple nodes simultaneously, the Administration Server domain directory can be shared with other managed servers. In addition, it can be failed over independently of the Node1 Admin Server EM Admin Server Node2 Admin Server EM Admin Server CompApp1 CompApp2 Managed Server Managed Server cfcvip.mycompany.com Shared Storage CompApp1 CompApp2 Middleware Home Middleware Home Admin Server Domain Directory 12-12 Oracle Fusion Middleware High Availability Guide Managed Server. The Administration Server can failover and Managed Servers can continue to run independently on their designated nodes. This is possible because the Administration Server in this case requires only failover of the VIP, and does not require failover of the shared disk. The domain directorydomain home continues to remain available by the Managed Servers. Example of such storage include a NAS or a SANDirect attached storage with Cluster file system. 2. If only one node can mount the shared storage a time, sharing the Administration Server domain directory with a Managed Server implies that when the Administration Server fails over, the Managed Server that runs off the same domain directory must be shut down. A hardware cluster may be used in this topology. The cluster helps automate failover when used with properly configured clusterware. However, it is not required. A single hardware cluster can be deployed to host these multiple Administration Servers. Each Administration Server can use its own virtual IP and set of shared disks to provide domain services high availability. This topology is supported for Oracle SOA Suite and Oracle WebCenter Suite only.

12.2.2.2.1 Topology 2 Installation Procedure To install and configure Cold Failover Cluster

for the Administration Server in this topology: Install the Middleware Home Install the Middleware Home including the Oracle Home and WebLogic Home separately on the two nodes of the domain. The Administration Server domain directory is created on a shared disk. This disk should be mountable by all the nodes that act as the failover destination for the Administration Server. Depending on the storage sub-system used, the shared disk may be mountable only on one node at a time. This is a regular single-instance installation. Refer to the product suite for details on installing the Administration Server, and Enterprise Manager alone. To install the Middleware Home: For Oracle SOA Suite or Oracle WebCenter: 1. Install the Oracle WebLogic Server software on Node 1. 2. Install the Oracle Home for SOA or WebCenter on Node 1. 3. Repeat steps 1 and 2 on Node 2. 4. Start the Configuration Wizard on Node 1 and create a domain with just the Administration Server. In the Select Domain Source screen, select the following: ■ Generate a domain configured automatically to support the following products . ■ Select Enterprise Manager and Oracle JRF. 5. In the Specify Domain Name and Location screen, enter the domain name, and be sure the domain directory matches the directory and shared storage mount point. Note: For the Oracle Identity Management, an alternate topology is also supported for Cold Failover Cluster. See the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management for more details. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-13 Configuring the Middleware Home for Cold Failover Cluster To configure the Middleware Home for Cold Failover Cluster: 1. Provision the Virtual IP. For example: For Linux: ifconfig eth0:1 IP_Address netmask netmask sbinarping -q -U -c 3 -I eth0 IP_Address Where IP_Address is the virtual IP address and the netmask is the associated netmask. In the following example, the IP address is being enabled on the interface eth0. ifconfig eth0:1 130.35.46.17 netmask 255.255.224.0 sbinarping -q -U -c 3 -I eth0 130.35.46.17 For Windows: netsh interface ip add address interface IP_Adress netmask Where IP_Address is the virtual IP address and the netmask is the associated netmask. In the example below, the IP address is being enabled on the interface Local Area Connection. netsh interface ip add address Local Area connection 130.35.46.17 255.255.224.0 2. Transform the Administration Server instance to Cold Failover Cluster using the procedure in Section 12.2.2.3, Transforming the Administration Server for Cold Failover Cluster. 3. Validate the Administration Server by accessing the consoles on the virtual IP. http:cfcvip.mycompany.com:7001console http:cfcvip.mycompany.com:7001em 4. Failover the Administration Server manually to the second node: a. Stop the Administration Server process and any other process running out of a given Middleware Home. b. Unmount the shared storage from Node1 where the Middleware Home or domain directory exists. c. Mount the shared storage on Node2, following storage specific commands. d. Disable the virtual IP on Node1: For Linux: ifconfig interface:index down In the following example, the IP address is being disabled on the interface eth0. ifconfig eth0:1 down For Windows: netsh interface ip delete address interface addr=IP Address Where IP Address is the virtual IP address. In the following example, the IP address is enabled on the interface Local Area Connection. 12-14 Oracle Fusion Middleware High Availability Guide netsh interface ip delete address Local Area connection addr=130.35.46.17 DOMAIN_HOME binstartWebLogic.sh Where DOMAIN_HOME is the location of your domain directory. e. Enable the virtual IP on Node 2. f. Start the Administration Server process using the following command: DOMAIN_HOME binstartWebLogic.sh Where DOMAIN_HOME is the location of your domain directory. g. Validate access to both Administration Server and Enterprise Manager console.

12.2.2.3 Transforming the Administration Server for Cold Failover Cluster