In the Environment section, select Servers. Select Protocols, then select HTTP. In the Frontend Host field, enter the host name as cfcvip.mycompany.com. Click Save.

12-28 Oracle Fusion Middleware High Availability Guide In many Cold Failover Cluster deployments OWSM-PM is deployed to the Administration Server, however, they can be deployed to a managed server by itself, for example, WLS_OWSM, or to the SOA managed server. The WLS_SOA container may have applications such as BPEL, UMS, and B2B deployed or may additionally have the BPM components deployed as well. In all cases, since these are Java EE components, the Cold Failover Cluster transformation procedure involves configuring the managed server to which they are deployed to listen on the virtual IP. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for information on transforming managed servers WLS_OWSM and WLS_SOA. In addition, follow these steps to transform a SOA component managed server: 1. Set the front-end host for WLS_SOA managed server to cfcvip.mycompany.com. a. Log into Oracle WebLogic Server Administration Console.

b. In the Environment section, select Servers.

c. Select the name of the managed server.

d. Select Protocols, then select HTTP.

e. In the Frontend Host field, enter the host name as cfcvip.mycompany.com.

f. Set the Frontend Port to the HTTP port

g. Click Save.

h. Activate the changes. i. Restart the Managed Server. 2. When using Oracle HTTP Server as the front end, the mod WebLogic configuration for the applications deployed to WLS_OWSM and WLS_SOA should provide the VIP cfcvip.mycompany.com as the address of these managed server. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used by SOA components. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: SOA soa-infra app Location soa-infra SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Worklist Location integration SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location B2B Location b2b SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location UMS Location sdpmessaging SetHandler weblogic-handler WebLogicHost cfc.mycompany.com:port Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-29 Location UMS WS Location ucsmessagingwebservice SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location WSM Location wsm-pm SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location workflow Location workflow SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Required if attachments are added for workflow tasks Location ADFAttachmentHelper SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Required if SOA is being used for Oracle Image and Process Management SOA inspection.wsil Location inspection.wsil SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location

12.2.3.6 Transforming Oracle Access Manager and Its Clients

This section describes how to transform Oracle Access Manager to work in a Cold Failover Cluster environment. As with other managed servers created using Configuration Wizard, a Cold Failover Cluster set up that requires the managed server to listen on a virtual IP can be done during the initial creation as well by specifying the listen address of the managed server as the virtual hostname cfcvip.mycompany.com. In this case, the explicit transformation step is not needed.

12.2.3.6.1 Transforming Oracle Access Manager Oracle Access Manager is deployed to a

managed server for example, WLS_OAM1 and the procedure for CFC transformation is to configure this managed server to listen on the virtual IP cfcvip.mycompany.com. Follow the steps in Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers to configure the WLS_OAM1 managed server to listen on the cfcvip.mycompany.com virtual IP. All other requirements related to the placement of the Middleware Home and other related domain artifacts on a shared storage that can be failed over apply, as described in Section 12.2.1, General Requirements for Cold Failover Cluster. 12-30 Oracle Fusion Middleware High Availability Guide The Oracle Access Manager console is deployed as part of the Administration Server for the domain. For Cold Failover Cluster configuration of this console, the whole Administration Server needs to be configured in Active Passive. The Administration Server could share the same virtual IP cfcvip.mycompany.com, or it could be configured to fail over independently using a separate virtual IP and shared disk. If they are using the same virtual IP, the Administration Server and the Oracle Access Manager managed server will fail over as a unit.

12.2.3.6.2 Transforming Oracle Access Manager Clients Follow these steps to transform

Oracle Access Manager clients: 1. Clients of Oracle Access Manager must use the virtual IP cfcvip.mycompany.com to access these applications. Any wiring done with other components such as Oracle Identity Manager and Oracle Adaptive Access Manager should also use the virtual IP cfcvip.mycompany.com to access the applications. 2. When Oracle HTTP Server is the front end for Oracle Access Manager, the mod webLogic configuration for Oracle Access Manager must specify the virtual IP cfcvip.mycompany.com as the address for the Oracle Access Manager managed server. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: Oracle Access Manager Location oam SetHandler weblogic-handler WebLogicHost cfvcip.mycompany.com:port Location 3. When the Oracle Access Manager console as part of the Oracle Administration Server is also configured to be Active Passive, and the Administration Server is configured to be front-ended by Oracle HTTP Server, you must change the WebLogic host configuration in the webserver proxy plugin configuration files. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: Oracle Access Manager Admin Console deployed to the Admin Server Location oamconsole SetHandler weblogic-handler WebLogicHost ADMINVHN WebLogicPort 7001 Location

12.2.3.7 Transforming Oracle Adaptive Access Manager and Its Clients

This section describes how to transform Oracle Adaptive Access Manager to work in a Cold Failover Cluster environment. As with other managed servers created using Configuration Wizard, a Cold Failover Cluster set up that requires the managed server to listen on a virtual IP can be done during the initial creation as well by specifying the listen address of the managed server as the virtual hostname cfcvip.mycompany.com. In this case, the explicit transformation step is not needed.

12.2.3.7.1 Transforming Oracle Adaptive Access Manager Oracle Adaptive Access Manager

is deployed to managed servers, both deployed to fail over as a single unit, and therefore sharing the same virtual IP and the same shared storage. The procedure to convert the OAAM Admin managed server and the OAAM Server managed server for Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-31 CFC transformation is to configure these managed servers to listen on the virtual IP cfcvip.mycompany.com. Follow the steps in Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers to configure these managed servers to listen on the cfcvip.mycompany.com virtual IP. All other requirements related to the placement of the Middleware Home and other related domain artifacts on a shared storage that can be failed over apply, as described in Section 12.2.1, General Requirements for Cold Failover Cluster.

12.2.3.7.2 Transforming Oracle Adaptive Access Manager Clients Follow these steps to

transform Oracle Adaptive Access Manager clients: 1. Clients of Oracle Adaptive Access Manager must use the virtual IP cfcvip.mycompany.com to access these applications. Any wiring done with other components such as Oracle Access Manager and Oracle Identity Manager should also use the virtual IP cfcvip.mycompany.com to access the applications. 2. When Oracle HTTP Server is the front end for Oracle Adaptive Access Manager, the mod webLogic configuration for Oracle Adaptive Access Manager must specify the virtual IP cfcvip.mycompany.com as the address for the Oracle Adaptive Access Manager managed servers. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used. For example, use a text editor to make the following edits in the mod_ wl_ohs.conf file: Oracle Adaptive Access Manager Location oaam_server SetHandler weblogic-handler WebLogicHost cfvcip.mycompany.com:port Location Oracle Adaptive Access Manager Admin Console Location oaam_admin SetHandler weblogic-handler WebLogicHost cfvcip.mycompany.com:port Location

12.2.3.8 Transforming Oracle Identity Manager and Its Clients

This section describes how to transform Oracle Identity Manager to work in a Cold Failover Cluster environment. As with other managed servers created using Configuration Wizard, a Cold Failover Cluster set up that requires the managed server to listen on a virtual IP can be done during the initial creation as well by specifying the listen address of the managed server as the virtual hostname cfcvip.mycompany.com. In this case, the explicit transformation step is not needed.

12.2.3.8.1 Transforming Oracle Identity Manager Oracle Identity Manager is deployed to

managed servers. The typical CFC deployment will have the Oracle Identity Manager managed server and the another managed server with Oracle SOA and Oracle Web Services Manager deployed to fail over as a single unit and therefore sharing the same virtual IP and the same shared storage. The procedure to convert both these managed server for CFC transformation is to configure this managed servers to listen on the virtual IP cfcvip.mycompany.com. Follow the steps in Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers to configure these managed servers to listen on the cfcvip.mycompany.com virtual IP. All other requirements related to the placement of the Middleware Home and other related domain artifacts on a shared storage that 12-32 Oracle Fusion Middleware High Availability Guide can be failed over apply, as described in Section 12.2.1, General Requirements for Cold Failover Cluster.

12.2.3.8.2 Transforming Oracle Identity Manager Clients Follow these steps to transform

Oracle Identity Manager clients: 1. Clients of Oracle Identity Manager must use the virtual IP cfcvip.mycompany.com to access these applications. Any wiring done with other components such as Oracle Access Manager and Oracle Adaptive Access Manager should also use the virtual IP cfcvip.mycompany.com to access the applications. Since SOA is also configured to fail over with Oracle Identity Manager, the wiring from Oracle Identity Manager to SOA should also use the common virtual IP. 2. When Oracle HTTP Server is the front end for Oracle Identity Manager, the mod webLogic configuration for Oracle Identity Manager must specify the virtual IP cfcvip.mycompany.com as the address for the managed servers. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file or oim.conf file: Oracle Identity Manager Location oim SetHandler weblogic-handler WebLogicHost cfvcip.mycompany.com:port Location Refer to Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager for more information about making configuration changes in Oracle Identity Manager.

12.2.3.9 Transforming an Oracle WebCenter Suite

The WebCenter Suite is made up of Java EE components. The typical WebCenter Suite deployment has four managed servers, though more are possible if you develop WebCenter Portal applications. Typical managed server deployments include: ■ WC_SPACES ■ WC_PORTLETS ■ WC_COLLABORATION ■ WC_UTILITIES These are Java EE components, therefore, the procedure for Cold Failover Cluster transformation is to configure the Managed Server they are deployed to so that it listens on the Virtual IP. In many Cold Failover Cluster deployments of Oracle WebCenter, OWSM-PM may be deployed to WC_PORTLETS and WC_SPACES container. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for information on transforming Oracle WebCenter Suite managed servers. When you use Oracle HTTP Server as the front end, the mod_weblogic configuration for WebCenter Suite applications should provide the VIP cfcvip.mycompany.com as the managed servers address instead. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points that WebCenter components use. To use a virtual host as the managed servers address: 1. Verify that the Virtual Host CFCVIP is enabled on the machine that the managed server runs on. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-33 2. Verify that the managed server Listen Address is set to CFCVIP. 3. Use the CFCVIP address in the mod_wl_ohs.conf file.

12.2.3.10 Transforming Oracle Portal, Forms, Reports, and Discoverer

Cold Failover Cluster configuration varies for each Oracle Portal, Forms, Reports, and Discoverer component. This section documents the steps for Cold Failover Cluster transformation of Oracle Portal, Forms, Reports, and Discoverer.

12.2.3.10.1 Transforming Oracle Forms for Cold Failover Cluster Oracle Forms is made up of

both Java EE and system components. To configure Oracle Forms for Cold Failover Cluster:

1. Transform the WLS_FORMS managed server. See

Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for this procedure. Start the Domain Administration Server to do the Managed server transformation, and shut it down once the Managed Server transformation is finished.

2. Transform the Oracle Forms OPMN. See

Section 12.2.2.6, Transforming Oracle Process Management and Notification Server for this procedure.

3. Transform Enterprise Manager. See

Section 12.2.2.7, Transforming Oracle Enterprise Manager for an Oracle Instance for this procedure.

4. Transform Oracle Forms Web tier components. See

Section 12.2.2.8, Transforming Web Tier Components and Clients for this procedure.

5. Reregister Single Sign-On using the steps described in the

Section 14.6.4.9.4, Enable Single Sign On.

6. In the forms.conf file located in the INSTANCE_

HOMEconfigOHSohs1moduleconf directory, change the mod weblogic configuration. Start the Administration Server and Managed Servers in the WebLogic Domain as well as the Oracle instances to validate the Cold Failover Cluster installation: Location Forms SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port DynamicServerList OFF Location

12.2.3.10.2 Transforming Oracle Reports for Cold Failover Cluster Oracle Reports is made up

of both Java EE and system components. To configure Oracle Reports for Cold Failover Cluster:

1. Transform the WLS_REPORTS managed server. See

Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for this procedure. Start the Domain Administration Server to do the Managed Server transformation, and shut it down once the Managed Server transformation is finished.

2. Transform the Oracle Reports OPMN. See

Section 12.2.2.6, Transforming Oracle Process Management and Notification Server for this procedure Note: The transformation process requires that you shutdown the domain before editing these files. 12-34 Oracle Fusion Middleware High Availability Guide In addition, do the following: a. In the opmn.xml file, located in the INSTANCE_ HOMEconfigOPMNopmn, directory, change the Reports server name in ias-component to reflect its new name. For example: ias-component id=ReportsServer_virtual_hostname_instance_name process-set id=ReportsServer_virtual_hostname_instance_name restart-on-death=true numprocs=1 ias-component For example: ias-component id=ReportsServer_cfcvip_asinst1 process-set id=ReportsServer_ cfcvip asinst1restart-on-death=true numprocs=1 ias-component b. In DOMAIN_HOMEopmntopology.xml of the Administration Server domain home, change all occurrences of the Report server name from ReportsServer_physical hostname_instance_name example: ReportServer_ node1_asinst to ReportsServer_virtual_hostname_instance_name example: ReportServer_cfcvip_asinst 3. Transform Oracle Enterprise Manager. See Section 12.2.2.7, Transforming Oracle Enterprise Manager for an Oracle Instance for this procedure. 4. Transform Oracle Reports Web tier components. See Section 12.2.2.8, Transforming Web Tier Components and Clients for this procedure. 5. Reregister Single Sign-On. To do this perform the steps described in the Section 14.6.4.9.4, Enable Single Sign On. 6. In the reports_ohs.conf file located in the INSTANCE_ HOMEconfigOHSohs1moduleconf directory, change the following: Location reports SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location 7. In the directory INSTANCE_HOMEconfigReportsServerComponent, rename the following directory: ReportsServer_physical_hostname_instance_name for example: ReportServer_node1_ asinst To the following: ReportsServer_VIP_instance_name for example: ReportServer_cfcvip_asinst 8. In the renamed directory, replace physical hostname with a virtual hostname in the following files: ■ component-logs.xml Note: All new logs for the report server go to ReportsServer_Virtual_ Hostname_Instance_Name after restart of the instance. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-35 ■ logging.xml 9. In the targets.xml file, located in the INSTANCE_ HOMEEMAGENTemagent_dirsysmanemd directory, change the following: a. Change all hostnames from node1.mycompany.com to cfcvip.mycompany.com b. Change the report server name from ReportsServer_physical_ hostname_instance_name for example: ReportServer_node1_ asinst to ReportsServer_VIP_instance_name for example: ReportServer_cfcvip_asinst for the following two elements: Target TYPE=oracle_repserv Target TYPE=oracle_repapp 10. In the INSTANCE_HOMEreports directory, replace the physical hostname with a virtual hostname in reports_install.properties. 11. In the INSTANCE_HOMEreportsserver directory, rename the following files: ■ Rename reportsserver_physical hostname_instance name.dat to reportsserver_ virtual host name_instance name.dat ■ Rename rep_wls_reports_physical hostname_instance name.dat to rep_wls_ reports_virtual hostname_instance name.dat 12. In the DOMAIN_HOMEserversWLS_REPORTStmp_WL_userreports_ version_number1ww3jmconfiguration directory for example, the DOMAIN_ HOMEserversWLS_REPORTStmp_WL_userreports_ 11.1.1.3.01ww3jmconfiguration directory, replace physical hostname with virtual hostname in the rwservlet.properties file including changes to any occurrence of the reports server name. 13. In the DOMAIN_HOMEserversWLS_REPORTStmp_WL_userreports_ version_number1ww3jmMETA-INF directory for example, the DOMAIN_ HOMEserversWLS_REPORTStmp_WL_userreports_ 11.1.1.3.01ww3jmMETA-INF directory, replace physical hostname with virtual hostname in the mbeans.xml file including changes to any occurrence of the reports server name. 14. Start the Administration Server and Managed Servers in the WebLogic Domain, as well as the Oracle instances to validate the Cold Failover Cluster installation.

12.2.3.10.3 Transforming Oracle Discoverer for Cold Failover Cluster Oracle Discoverer is

made up of both Java EE and system components. To configure Oracle Discoverer for Cold Failover Cluster: 1. Transform the WLS_DISCO managed server. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for this procedure. Start the domain Administration Server to do the Managed Server transformation, and shut it down once the Managed Server transformation is finished. 2. Transform the Oracle Discoverer OPMN. See Section 12.2.2.6, Transforming Oracle Process Management and Notification Server for this procedure. 3. Transform Oracle Enterprise Manager. See Section 12.2.2.7, Transforming Oracle Enterprise Manager for an Oracle Instance for this procedure. 4. Transform Oracle Discoverer Web tier components. See Section 12.2.2.8, Transforming Web Tier Components and Clients for this procedure. 12-36 Oracle Fusion Middleware High Availability Guide 5. Reregister Single Sign-On. To do this perform the steps described in the Section 14.6.4.9.4, Enable Single Sign On. 6. In the reports_ohs.conf file located in the INSTANCE_ HOMEconfigOHSohs1moduleconf directory, change the following: IfModule mod_weblogic.c Location discoverer SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port DynamicServerList ON Location IfModule

12.2.3.10.4 Transforming Oracle Portal for Cold Failover Cluster Oracle Portal is made up of

both Java EE and system components. To configure Oracle Portal for Cold Failover Cluster: 1. Transform the WLS_PORTAL managed server. See Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers for this procedure. Start the domain Administration Server to do the Managed Server transformation, and shut it down once the Managed Server transformation is finished. 2. Transform the Oracle Portal OPMN. See Section 12.2.2.6, Transforming Oracle Process Management and Notification Server for this procedure. 3. Transform Oracle Enterprise Manager. See Section 12.2.2.7, Transforming Oracle Enterprise Manager for an Oracle Instance for this procedure. 4. Transform Oracle Portal Web tier components. See Section 12.2.2.8, Transforming Web Tier Components and Clients for this procedure. 5. Reregister Single Sign-On. To do this, perform the steps described in the Section 14.6.4.9.4, Enable Single Sign On. 6. In the portal.conf file located in the INSTANCE_ HOMEconfigconfigOHSohs1moduleconf, change the mod weblogic configuration, change the mod weblogic configuration: WLS routing configuration Location portal SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Location portalTools SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Location wsrp-tools SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Location richtextportlet SetHandler weblogic-handler Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-37 WebLogicHost cfcvip.mycompany.com WebLogic port Location Location jpdk SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Location portalHelp SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location Location portalHelp2 SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location 7. Rewire the Portal Repository: a. Log into the domain WebLogic Server Enterprise Manager using the following URL: http:cfcvip.mycompany.com:7001em b. Change InValidation and Administrator password. In the Navigator Window Expand the Web Tier tree. Click the component wc1. From the drop-down list at the top of the page, select Administration - Passwords . Enter a new invalidation password, confirm it, and click Apply. Enter a new administrator password, confirm it and click Apply.

c. Expand the Fusion Middleware menu in the left pane.