Administration Server Topology 1 Transforming Oracle Fusion Middleware Infrastructure Components

12-8 Oracle Fusion Middleware High Availability Guide

12.2.2.1 Administration Server Topology 1

Figure 12–1 illustrates the first supported topology for Oracle Cold Failover Cluster. Figure 12–1 Administration Server Cold Failover Cluster Topology 1 In Figure 12–1 , 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 Middleware Home and the domain directory is on a shared disk that is mounted on Node 1 or Node 2 at any given point. Both the Middleware home and the domain directory should be on the same shared disk or shared disks that can fail over together. If an enterprise has multiple Fusion Middleware domains for multiple applications or environments, this topology is well suited for Administration Server high availability. 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 high availability of domain services.

12.2.2.1.1 Topology 1 Installation Procedure To install and configure Cold Failover Cluster

for the application server in this topology: Install the Middleware Home This installation includes the Oracle home, WebLogic home, and the Domain home 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 the preferred configuration, even when the storage sub system allows simultaneous mounts on more than one node. This is done as a regular single-instance installation. Please refer to the component chapters for details on installing the Administration Server and Enterprise Manager alone. The overall procedure for each suite is as follows: For Oracle SOA or Oracle WebCenter: 1. Install the WebLogic Server software. See the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server. 2. Install the Oracle Home for Oracle SOA or WebCenter. See the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite or the Oracle Fusion Middleware Installation Guide for Oracle WebCenter. Node1 AdminServer Admin Server FMW Control CRS Node2 AdminServer Admin Server FMW Control CRS Shared Storage Middleware Home Interconnect cfcvip.mycompany.com Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-9 3. Invoke the Configuration Wizard 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. For Oracle Identity Management: 1. Install the WebLogic Server software. See the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server. 2. Using Oracle Identity Management 11g Installer, install and configure the IDM Domain using the create domain option. In the Configure Components Screen, de-select everything except Enterprise Manager selected by default See the Oracle Fusion Middleware Installation Guide for Oracle Identity Management. For Oracle Portal, Forms, Reports and Discoverer: 1. Install the WebLogic Server software. See the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server. 2. Using Oracle Fusion Middleware 11g Portal, Forms, Reports, and Discoverer Installer, install and configure the Classic Domain using the create domain option. In the Configure Components Screen, ensure that Enterprise Manager is also selected. For Oracle Business Intelligence: 1. Install the WebLogic Server software. See the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server. 2. Using Oracle Fusion Middleware 11g Business Intelligence Installer, install and configure the Business Intelligence domain using the create new BI system option. Configuring the Administration Server for Cold Failover Cluster To configure the Administration Server for Cold Failover Cluster: 1. Provision the Virtual IP using the following commands as root user: For Linux sbinifconfig interface:index IP_Address netmask netmask Note: In this case, at least one more Managed Server for the product components is also installed in this process the Administration Server by itself cannot be installed. This Managed Server must also be transformed to CFC using the specific procedure for the component. It is part of the same failover unit as the Administration Server. Note: In this case, at least one more Managed Server for the product components is also installed in this process the Administration Server by itself cannot be installed. This Managed Server must also be transformed to CFC using the specific procedure for the component. It is part of the same failover unit as the Administration Server. 12-10 Oracle Fusion Middleware High Availability Guide sbinarping -q -U -c 3 -I interface 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 Address 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 following the procedure in section Section 12.2.2.3, Transforming the Administration Server for Cold Failover Cluster. 3. Validate the Administration Server transformation 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 using the following procedure: 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 and domain directory exists. c. Mount the shared storage on Node2, follow storage specific commands. d. Disable the Virtual IP on Node1 using the following command as root user: For Linux: sbinifconfig interface:index down Where IP Address is the virtual IP. In the example below, the IP address is being disabled on the interface eth0. sbinifconfig eth0:1 down On Windows: netsh interface ip delete address interface IP_Address 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 delete address Local Area connection 130.35.46.17 e. Enable the virtual IP on Node2 using similar commands as in Step 1. 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