Server Properties Identity Provider Common Service Provider Common Data Stores Authentication Engine LDAP Directory

Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-27 Cluster transformation is to configure the Managed Server to which it is deployed to listen on the cfcvip.mycompany.com virtual IP. Follow the steps in Section 12.2.2.4, Transforming Oracle WebLogic Managed Servers to configure the WLS_OIF Managed Server to listen on the cfcvip.mycompany.com virtual IP. Since Oracle Identity Federation Cold Failover Cluster deployments are likely to be split into Service Provider and Identity Provider, more than one instance of WLS_OIF is likely to exist in a given deployment. Use the same Cold Failover Cluster procedure for both WLS_OIF instances. After configuring the Managed Server to listen on the cfcvip.mycompany.com virtual IP, log into the Oracle Enterprise Manager Fusion Middleware Control and perform these steps:

1. Navigate to Farm Identity and Access OIF.

2. In the right frame, navigate to Oracle Identity Federation Administration and

then make these changes:

a. Server Properties

: change the host to cfcvip.mycompany.com

b. Identity Provider Common

: change the providerId to cfcvip.mycompany.com

c. Service Provider Common

: change the providerId to cfcvip.mycompany.com

d. Data Stores

: If LDAP is the data store, then replace the value of Connection URL for User Data Store and Federation Data Store with cfcvip.mycompany.com

e. Authentication Engine LDAP Directory

: Set the ConnectionURL to cfcvip.mycompany.com The metadata needs to be generated after the above changes are done.

12.2.3.4.2 Transforming Oracle Identity Federation Clients Follow these steps to transform

Oracle Identity Federation clients: 1. Clients of Oracle Identity Federation must use the virtual IP cfcvip.mycompany.com to access these applications. 2. When Oracle HTTP Server is the front end for Oracle Identity Federation, the WebLogic configuration for Oracle Directory Services Manager must specify the virtual IP cfcvip.mycompany.com as the address for the WLS_OIF Managed Server. To do this, change the WebLogic host configuration in the webserver proxy plugin configuration files for the mount points used by Oracle HTTP Server and Oracle Directory Services Manager. For example, use a text editor to make the following edits in the mod_wl_ohs.conf file: Oracle Identity Federation Location oif SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com WebLogic port Location

12.2.3.5 Transforming an Oracle SOA Suite

Oracle SOA Suite is made up of Java EE components deployed to a managed server. The typical configuration has deployments of OWSM-PM applications and SOA applications. The SOA applications are always deployed to a separate managed server. 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.