Select Environment, and then Machines. In the Change Center, click Lock Edit. Click New. In the Name field, enter cfcvip.mycompany.com Click OK. Click the Servers tab. Click Add. Click Activate Changes. Select Environment, and then Servers from the Domai

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

To transform the Administration Server installed on a shared disk from Node 1, follow the steps in this section. These step transform the container, therefore, both the WebLogic Server Administration Console and Oracle Enterprise Manager Fusion Middleware Control, are transformed for Cold Failover Cluster. This results in other components such as OWSM-PM, deployed to this container, to become Cold Failover Cluster ready as well. The address for all of these services transforms cfcvip.mycompany.com. After installation, to transform a non Cold Failover Cluster instance, to a Cold Failover Cluster: 1. Log into the WebLogic Server Administration Console. 2. Create a Machine for the Virtual Host

a. Select Environment, and then Machines.

b. In the Change Center, click Lock Edit.

c. Click New.

d. In the Name field, enter cfcvip.mycompany.com

e. Select the appropriate operating system.

f. Click OK.

g. On the Summary of Machines tab, click the machine name just created.

h. Click the Servers tab.

i. Click Add.

j. Select an existing server, and associate it with this machine. In the select server drop down list ensure AdminServer is selected.

k. Click Activate Changes.

3. Configure the Administration Server to Listen on cfcvip.mycompany.com.

a. Select Environment, and then Servers from the Domain Structure menu.

b. In the Change Center, click Lock Edit.

c. Click on the Administration Server AdminServer

d. Change the Listen Address to cfcvip.mycompany.com

e. Click Save.

f. Click Activate Changes.

Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-15 g. Restart the Administration Server. Changing Client Side Configuration for Administration Server Any existing entities in the domain must communicate with the Administration Server using the new address. For example, when starting the Managed Servers manually, the Administration Server address should be specified as cfcvip.mycompany.com. In the instance.properties file, located in the INSTANCE_HOMEOPMNopmn directory, make the following change: adminHost=cfcvip.mycompany.com If the Oracle Instance is to be registered or re-registered with a Cold Failover Cluster Administration Server using the OPMN registration commands, the AdminHost location in the opmnctl command should reference the new location of the Administration Server cfcvip.mycompany.com. Changing Client Side Configuration for Oracle Enterprise Manager Since the Enterprise Manager is part of the same container where the Administration Server runs, transforming the Administration Server to Cold Failover Cluster also transforms the Enterprise Manager. If there are existing Enterprise Manager Agents configured to be part of the domain, these agent configurations must use the new location for the Enterprise Manager. To configure the new location for Enterprise Manager, use the following steps for each agent: 1. Set the directory to ORACLE_INSTANCEEMAGENTemagent_asinst_ 1sysmanconfig. 2. In the emd.properties file, change node1.mycompany.com to cfcvip.mycompany.com in the following attributes: ■ REPOSITORY_URL ■ EmdWalletSrcUrl 3. Stop and restart the agent using the following commands: cd INSTANCE_HOMEEMAGENTemagent_dirbin .emctl stop agent .emctl start agent .emctl status agent This shows the Repository URL and it should now point to the new host.

12.2.2.4 Transforming Oracle WebLogic Managed Servers

All Oracle Fusion Middleware components are deployed to a Managed Server. An important step to convert an application or component that is deployed to Oracle WebLogic Server to Cold Failover Cluster is to change its listen address to the virtual IP being used. This change is done for the specific Managed Server to which the Note: Since it is typically expected that transformation to Cold Failover Cluster for the Administration Server is done at domain creation time No other changes to other parts of the domain are expected. If this change happens post domain creation, and other components are installed in the domain, follow the steps in the following Administration Server transformation section. 12-16 Oracle Fusion Middleware High Availability Guide component has been deployed. You can make this change using the WebLogic Server Administration Console or using WLST commands. The following example describes the generic steps for Cold Failover Cluster transformation of a Managed Server named WLS_EXMPL. These steps apply to any Managed Server in the Fusion Middleware components.

12.2.2.4.1 Transforming an Oracle WebLogic Managed Server using the Fusion Middleware

Administration Console For this procedure, the WebLogic Server Administration Console must be running. In the following example, cfcvip.mycompany.com is the virtual IP used for the Cold Failover Cluster, and WLS_EXMPL is the managed server to be transformed. 1. Log into the WebLogic Server Administration Console. 2. Create a machine for the virtual host:

a. Select Environment Machines.