Click Activate Changes. Choose Environment Servers. Click Control. Select WLS_EXMPL. Click Start.

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.

b. In the Change Center, click Lock Edit.

c. Click New.

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

e. For the Machine OS field, select the appropriate operating system.

f. Click OK.

g. Click the newly created Machine.

h. Click Node Manager tab.

i. Update Listen Address: cfcvip.mycompany.com.

j. Click Save.

k. Click Activate Changes.

3. Stop the WLS_EXMPL Managed server:

a. Choose Environment Servers.

b. Click Control.

c. Select WLS_EXMPL.

d. Select Force Shutdown Now in the Shutdown drop-down menu.

4. Associate the WLS_EXMPL Managed Server with the VirtualHost Machine:

a. Choose Environment Servers.

b. In the Change Center, click Lock Edit.

c. Click Configuration.

d. Select WLS_EXMPL.

e. For Machine, assign the newly created Machine by assigning it from the pull down menu.

f. For Listen Address, enter cfcvip.mycompany.com.

g. Click Save.

h. Click Activate Changes.

5. Start the WLS_EXMPL Managed Server: Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-17

a. Choose Environment Servers.

b. Click Control.

c. Select WLS_EXMPL.

d. Click Start.

12.2.2.4.2 Transforming an Oracle WebLogic Managed Server using the WLST Command Line

You can transform an Oracle WebLogic managed server using WLST commands as well. Oracle recommends shutting down the managed server you are transforming before performing these steps. To transform a Managed Server using the WLST command line in online mode with the WebLogic Server Administration Server up: 1. In the command line, enter: WL_HOME serverbinsetWLSEnv.sh WL_HOME commonbinwlst.sh 2. In WLST, enter the following commands: wls:offlineconnectusername,password,AdminServer location For example: wls:offlineconnectWebLogic, welcome1, t3:admin.mycompany.com:7001 wls:DomainNameserverConfig edit wls:DomainNameedit startEdit wls:DomainNameedit createcfcvip.mycompany.com,Machine wls:DomainNameedit cdMachinescfcvip.mycompany.comNodeManagercfcvip.mycompany.com wls:DomainNameedit setListenAddress, cfcvip.mycompany.com wls:DomainNameedit cd Servers wls:DomainNameeditServers cd WLS_EXMPL wls:DomainNameeditServersWLS_EXMPL setMachine, cfcvip.mycompany.com wls:DomainNameeditServersWLS_EXMPL setListenAddress, cfcvip.mycompany.com wls:DomainNameeditServersWLS_EXMPL save wls:DomainNameeditServersWLS_EXMPL activate wls:DomainNameeditServersWLS_EXMPL exit Stop if not already down and start the Managed server. Once the Managed server transformation is completed, all references to it should use the new Listen Address - cfcvip.mycompany.com. If Oracle HTTP Server serves as a front end to this Managed server, then any mod_wls_ohs configuration with mount points referring to applications in this Managed server should be changed to route to the new listening end point.

12.2.2.5 Transforming Node Manager

Node Manager can be used in a Cold Failover Cluster environment. The possible configurations are: ■ Using a Node Manager that listens on the virtual IP as well and fails over with the rest of the Cold Failover Cluster stack. With ASCRS based deployments, the Node Manager must be part of the same Middleware Home as where the Cold Failover 12-18 Oracle Fusion Middleware High Availability Guide Cluster Fusion Middleware instance is running. This Node Manager is assumed to be dedicated for this Fusion Middleware instance. In this case, Oracle recommends having additional Network Channels listening on the localhost configured. Other Node Managers may co-exist on the box listening on other ports. For more details, see Chapter 13, Using Oracle Cluster Ready Services. ■ A Node Manager that does not failover with the rest of the Cold Failover Cluster stack. In this case, Node Manager is not configured for Cold Failover Cluster and listens on all IPs on the machine, and not specifically on the virtual IP for Cold Failover Cluster. The failover nodes also have a similarly configured Node Manager already available and configured. The Machine associated with the WebLogic instance communicates with the Node Manager on the localhost. For more details, see the Oracle Fusion Middleware Node Manager Administrator’s Guide for Oracle WebLogic Server. For Cold Failover Cluster in general, port usage should be planned so that there are no port conflicts when failover occurs. To convert the Node Manager to Cold Failover Cluster: 1. If Node Manager is running, stop it. The nodemanager.properties file is created only after the first start of Node Manager. Restart the Node Manager if necessary. 2. In the nodemanager.properties file located in the WL_ HOMEcommonnodemanager directory, set the ListenAddress to the virtual IP. For example: ListenAddress=cfcvip.mycompany.com 3. Restart the Node Manager using the StartNodeManager.sh file, located in the WL_HOMEserverbin directory. For ASCRS based deployment, the Node Manager is started using WL_HOMEserverbincfcStartNodemanager.sh. See Chapter 13, Using Oracle Cluster Ready Services. for more details.

12.2.2.6 Transforming Oracle Process Management and Notification Server

Oracle Process Management and Notification Server OPMN is used for Process Management of system components and is part of the application server instance. Note: If needed, start the Node Manager only using the cfcStartNodemanager.sh script instead of the startNodeManager.sh script. Note: For WebLogic Managed Servers and Administration Servers, hostname verification may be enabled or disabled in a given installation. For CFC installation where hostname verification is enabled and Node Manager is managing these instances, the hostname verification step should use certificates for the virtual IP cfcvip.mycompany.com as part of these steps. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-19 Oracle recommends keeping the default OPMN configuration in a Cold Failover Cluster environment. No further steps are necessary for Cold Failover Cluster transformation of the OPMN process itself. If you are transforming an Oracle Instance for Cold Failover Cluster and it has already been registered with an Administration Server, make the following changes in these files: 1. In the topology.xml file in the DOMAIN_HOMEopmn directory of the Administration Server domain, change host name entries for this specific Oracle instance being transformed to Cold Failover Cluster to cfcvip.mycompany.com. For example, for an Oracle HTTP Server instance transformed to Cold Failover Cluster, set the following in the topology.xml file property name=HTTPMachine value=cfcvip.mycompany.com For the instance itself: ias-instance id=asinst instance-home=11gr1as3MWasinst host=cfcvip.mycompany.com port=6701 2. In the opmn.xml file in the INSTANCE_HOMEconfigOPMNopmn directory, replace the physicalhostname with cfcvip.mycompany.com: ias-componentias-component id=ReportsServer_physicalhostname_asinst_2 process-set id=ReportsServer_physicalhostname_asinst_2 restart-on-death=true numprocs=1 3. In the instance.properties file in the INSTANCE_HOMEconfigOPMNopmn directory, change adminHost=physical hostname to adminHost=cfcvip.mycompany.com.

12.2.2.7 Transforming Oracle Enterprise Manager for an Oracle Instance

When an Oracle instance such as Oracle Internet Directory, Oracle Virtual Directory, Web Tier components, and Oracle Portal, Forms, Reports, and Discoverer components is transformed to Cold Failover Cluster, the Enterprise Manager agent that is part of this Oracle instance must be transformed to Cold Failover Cluster as well. To transform the Enterprise Manager agent: 1. Stop the Enterprise Manager agent using the following command: cd INSTANCE_HOMEEMAGENTemagent_dirbin .emctl stop agent 2. Set the directory to ORACLE_INSTANCEEMAGENTemagent_instance namesysmanconfig. 3. In the emd.properties file, change node1.mycompany.com to cfcvip.mycompany.com for the emd_url attribute. 4. Change the targets.xml file on the agent side: cd INSTANCE_HOMEEMAGENTemagent_dircp targets.xml targets.xml.org Modify targets.xml so that it has only targets related to the host and oracle_emd. Remove all other entries. For example: Targets AGENT_TOKEN=ad4e5899e7341bfe8c36ac4459a4d569ddbf03bc Target TYPE=oracle_emd NAME=cfcvip.mycompany.com:port Target TYPE=host NAME=cfcvip.mycompany.com DISPLAY_ 12-20 Oracle Fusion Middleware High Availability Guide NAME=cfcvip.mycompany.com Targets 5. Stop and restart the agent cd INSTANCE_HOMEEMAGENTemagent_dirbin .emctl start agent Make the following changes for the Enterprise Manager server in the Administration Server domain directory: 1. Set your directory to MW_HOMEuser_projectsdomainsdomain_ namesysmanstate. 2. In the targets.xml file, located in MW_HOMEuser_projectsdomainsdomain_ namesysmanstate directory, modify the hostname from node1.mycompany.com to cfcvip.mycompany.com

12.2.2.8 Transforming Web Tier Components and Clients

The Web tier is made up of two primary components, Oracle HTTP Server and Oracle Web Cache. The next two sections describe how to transform Oracle HTTP Server and Oracle Web Cache for Cold Failover Cluster.

12.2.2.8.1 Transforming Oracle HTTP Server To transform Oracle HTTP Server for Cold

Failover Cluster: In INSTANCE_HOMEconfigOHScomponent_namehttpd.conf, change the following attributes Listen cfcvip.mycompany.com:port OHS_LISTEN_PORT Listen cfcvip.mycompany.com:port OHS_PROXY_PORT ServerName cfcvip.mycompany.com Also, perform a single sign-on reregistration, as described in Section 12.2.3.14, Single Sign-On Re-registration If required. Clients of Oracle HTTP Server If an Oracle Web Cache instance is routing to Oracle HTTP Server that has been transformed to Cold Failover Cluster, in INSTANCE_ HOMEconfigWebCachecomponent_namewebcache.xml, change the following attributes: Change node1.mycompany.com to cfcvip.mycompany.com, where node1.mycompany.com is the previous address of the Oracle HTTP server before transformation. HOST ID=h1 NAME=cfcvip.mycompany.com PORT=8888 LOADLIMIT=100 OSSTATE=ON HOST ID=h2 NAME=cfcvip.mycompany.com PORT=8890 LOADLIMIT=100 OSSTATE=ON SSLENABLED=SSL

12.2.2.8.2 Transforming Oracle Web Cache To transform an Oracle Web Cache for Cold

Failover Cluster: 1. Set up an alias to the physical hostname on both nodes of the cluster in etchosts. This is an alias to the IP address of the node. Set this in etchosts for Linux and Windows location for Windows. The alias name is wcprfx.mycompany.com For example, On node Node1, the etchosts file on UNIX, the entry would be n.n.n.n node1 node1.mycompany.com wcprfx wcprfx.mycompany.com