Click Administration. Click Scheduler Configuration under System Maintenance Click Apply.

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.

b. Click Scheduler Configuration under System Maintenance

c. Change Weblogic JNDI URL to t3:cfc.mycompany.com:9704

d. Click Apply.

Transform Managed Server Oracle BI Publisher is deployed to a managed server for example, BI_SERVER1, and the procedure for Cold Failover Cluster transformation is to configure this managed server after install 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 BI_SERVER1 managed server to listen on the cfcvip.mycompany.com virtual IP. Then restart the managed server using the WebLogic Server Administration Console or the WLST command line. All requirements related to the placement of the Middleware Home and other related domain artifacts on shared storage that can be failed over apply as described in Section 12.2.1, General Requirements for Cold Failover Cluster. The specific requirement for Cold Failover Cluster deployments of the Oracle BI Publisher is to ensure that the following artifacts are also on the shared disk and available on the same mount points on both nodes of the failover cluster. When configured in the default install, this happens implicitly: ■ Transaction logs and JMS persistence store ■ BI Publisher configuration folder ■ BI Publisher Catalog repository ■ BI Publisher Scheduler temp directory Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-45 BI EE Integration When you deploy BI Publisher and BI EE together, BI Publisher is integrated to use BI EE Presentation Services. In this setup, the BI EE deployment is typically also a Cold Failover Cluster deployment listening on the same virtual hostname, cfc.mycompany.com. In this case, you must change the BI Publisher configuration related to BI EE integration to ensure that BI Publisher discovers the BI EE Presentation Services on this new address. To do this: 1. Invoke the BI Publisher application URL http:hostname:portxmlpserver and log in. 2. Change the BI Scheduler JMS configuration:

a. Click Administration.