Click JDBC Connection under Data Sources.

Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-43

5. Click Apply.

6. Click Activate Changes.

7. Restart both the Managed servers and the System components using opmnctl. Transforming Oracle BI Enterprise Edition Clients Follow these steps to transform Oracle BI Enterprise Edition clients: 1. Oracle BI Enterprise Edition clients must use the virtual IP cfcvip.mycompany.com to access these applications. 2. Since WSM-PM is deployed to the same managed server, ensure that the client side configuration changes required for WSM-PM are also complete. 3. Configure other components in the BI Enterprise Edition product suite, such as Oracle BI Publisher, that use Oracle BI Enterprise Edition services to take advantage of these services using the virtual hostname. 4. In BI Publisher, data sources that refer to this BI Enterprise Edition instance should change or be created if new using the new virtual host. To change: a. Navigate to the BI Publisher Administration Console.

b. Click JDBC Connection under Data Sources.

c. Edit any Data source for BI Enterprise Edition for this instance to connect to cfcvip.mycompany.com. 5. Where BI Publisher is integrated with BIEE deployment, configure BI Publisher to discover the Presentation Services at the new virtual address. Check details for these in the BI publisher section of this chapter. 6. When Oracle HTTP Server is the front end for Oracle BI Enterprise Edition, use a text editor to update the mod_wl_ohs file to specify the virtual IP cfcvip.mycompany.com as the address for the Oracle BI Server managed server. See the following example: BIEE Analytics Location analytics SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com:port Location Location analytics-ws SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com:port Location Location bimiddleware SetHandler weblogic-handler WebLogicHost cfcvip.mycompany.com:port Location Special Considerations for Windows To achieve Cold Failover Cluster Deployment on a Windows platform: 1. Make the shared disk available on drive for example, E:\. 2. Install BI EE suite software-only install on node1 of the Windows Cluster on E:\. 12-44 Oracle Fusion Middleware High Availability Guide 3. Delete the software-only install from E:\ by removing the Middleware Home. 4. Failover the same shared disk to node2 and make it available on node2 as the same drive E:\. 5. Install BI EE suite software-only install on node2 of the Windows Cluster on E:\. 6. Invoke the OUI Configuration Wizard and create the WLS domain and the Oracle Instance on E:\. 7. Enable the Virtual IP on the current node node2 and perform the transformation steps for this BI suite install in Section 12.2.3.12.1, Transforming Oracle Business Intelligence Enterprise Edition and its Clients.

12.2.3.12.2 Transforming Oracle Business Intelligence Publisher and its Clients This section

describes how to transform Oracle Business Intelligence Publisher Oracle BI Publisher to work in a Cold Failover Cluster environment. Transforming Oracle Business Intelligence Publisher The following section describes how to transform Oracle BI Publisher to work in a Cold Failover Cluster environment. 1. Open the BI Publisher application at http:hostname:portxmlpserver and login. 2. Change the BI Scheduler s JMS configuration:

a. Click Administration.