Using Fusion Middleware Control to View System Component Availability Using the Administration Console to View Managed Server Availability

6 Deploying Oracle Business Intelligence for High Availability 6-1 6 Deploying Oracle Business Intelligence for High Availability This chapter provides information about how to configure Oracle Business Intelligence components for high availability. It also describes the functionality available in Fusion Middleware Control to manage system availability, and provides information about using the Cluster Manager in the Administration Tool. This chapter does not provide information about setting up additional high availability configuration for other components in the stack, including database tier, Web tier, Administration Server, and identity management availability. For more information about these topics and how they relate to Oracle Business Intelligence deployments, see the following documents: ■ Configuring High Availability for Oracle Business Intelligence and EPM in Oracle Fusion Middleware High Availability Guide explains how to implement high availability across the stack, including how to configure a fault tolerant HTTP load balancer and a highly available database for the Oracle Business Intelligence schemas ■ Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence explains how to deploy Oracle Business Intelligence based on an architectural blueprint that follows Oracle recommended best practices for security and high availability, including Web tier, database tier, Administration Server, and identity management availability This chapter includes the following topics: ■ Section 6.1, About Oracle Business Intelligence Components in a Clustered Environment ■ Section 6.2, Configuring Oracle Business Intelligence Components for High Availability ■ Section 6.3, Optional Configuration for Oracle Business Intelligence High Availability ■ Section 6.4, Using the Cluster Manager ■ Section 6.5, Troubleshooting an Oracle Business Intelligence Clustered Environment 6-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

6.1 About Oracle Business Intelligence Components in a Clustered Environment

Figure 6–1 shows the system components and Java components in a highly available Oracle Business Intelligence deployment. See Section 1.3.3, About Java Components and System Components for Oracle Business Intelligence for more information about system components and Java components. Figure 6–1 A Highly Available Oracle Business Intelligence Deployment In Figure 6–1 , the Oracle Business Intelligence Java components are deployed on the BI_SERVER1 and BI_SERVER2 Managed Servers on APPHOST1 and APPHOST2. These Managed Servers are configured in an Oracle WebLogic cluster. Deploying Oracle Business Intelligence for High Availability 6-3 Oracle BI Presentation Services, JavaHost, Oracle BI Cluster Controller, Oracle BI Scheduler, and Oracle BI Server are system components installed on APPHOST1 and APPHOST2 and configured as a cluster. The Cluster Controller and Oracle BI Scheduler on APPHOST2 are passive they are started but do not service requests and are only made active if APPHOST1 components fail. In the data tier, shared external storage is configured to store the Oracle BI Presentation Catalog, Oracle BI Server global cache, Oracle BI repository, and Oracle BI Scheduler script data.

6.1.1 Recommendations for Availability

In a production system, it is recommended that you deploy two or more instances of every component on two or more computers, so that each component type has an instance running on more than one computer for fault tolerance. This configuration provides redundancy for Managed Servers and system components, an essential requirement for high availability and failover. You can see whether the system has any single points of failure by using the Availability tab of the Capacity Management page in Fusion Middleware Control. See Section 6.1.2, Using Fusion Middleware Control to Identify Single Points of Failure for more information. You can also ensure high availability by configuring redundancy in the database tier Oracle RAC recommended, Web tier, and for the Administration Server. See Configuring High Availability for Oracle Business Intelligence and EPM in Oracle Fusion Middleware High Availability Guide for more information. Note also the following requirements: ■ All Oracle BI Servers participating in the cluster must be within the same domain and on the same LAN subnet. Geographically separated computers are not supported. ■ The clock on each server participating in a cluster must be kept in synchronization. Out-of-sync clocks can skew reporting.

6.1.2 Using Fusion Middleware Control to Identify Single Points of Failure

Before you begin this procedure, ensure that you are familiar with the information in Section 3.2, Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings. To identify single points of failure: 1. Go to the Business Intelligence Overview page, as described in Section 2.2.2, Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components. 2. Display the Availability tab of the Capacity Management page. On this page, you can view recommendations about whether to scale out system components or configure primarysecondary system components. Click the Help button on the page to access the page-level help for its elements. 3. If you must scale out the Oracle BI Server, Oracle BI JavaHost, or Oracle BI Presentation Services, then you can click Scale Out Selected in the Single Points of Failure section to go to the Scalability tab to scale out a system component. See Section 5.5, Using Fusion Middleware Control to Scale System Components for more information. 6-4 System Administrators Guide for Oracle Business Intelligence Enterprise Edition 4. If you have a Cluster Controller or Oracle BI Scheduler that must be configured, the Single Points of Failure table displays the message Configure PrimarySecondary. See Section 6.2.1, Using Fusion Middleware Control to Configure Primary and Secondary Instances for information about how to do this.

6.1.3 Achieving High Availability Using an Active-Passive Model

As an alternative to setting up the active-active configuration described in the previous sections, you can set up Oracle Business Intelligence in an active-passive configuration using Oracle Fusion Middleware Cold Failover Cluster Cold Failover Cluster. In a Cold Failover Cluster configuration, two or more application server instances are configured to serve the same application workload, but only one is active at any particular time. A two-node Cold Failover Cluster can be used to achieve active-passive availability for Oracle Business Intelligence. In a Cold Failover Cluster, one node is active while the other is passive, on standby. In the event that the active node fails, the standby node is activated, and Oracle Business Intelligence continues servicing clients from that node. All Oracle Business Intelligence components are failed over to the new active node. No Oracle Business Intelligence components run on the failed node after the failover. See Active-Passive Topologies for Oracle Fusion Middleware High Availability in Oracle Fusion Middleware High Availability Guide for detailed information.

6.2 Configuring Oracle Business Intelligence Components for High Availability

To configure Oracle Business Intelligence for high availability, you must ensure that the system has no single points of failure by scaling out the Oracle BI Server, Presentation Services, and the JavaHost so that you have at least two of each component type, distributed across at least two computers. You also must configure primary and secondary instances of the Cluster Controller and Oracle BI Scheduler, so that the primary and secondary instances for each component type are distributed across two different computers. Table 6–1 lists the tasks that you must perform to configure high availability for Oracle Business Intelligence. Table 6–1 Task Summary for Configuring High Availability Task Where to Go for More Information Horizontally scale out the Oracle Business Intelligence deployment so that it includes two computers with a full set of Java and system components on each host. This task includes running the Oracle Business Intelligence installer, configuring shared files and directories, and scaling out system components using Fusion Middleware Control. Section 5.3, Horizontally Scaling Oracle Business Intelligence Configure primary and secondary instances of the Cluster Controller and Oracle BI Scheduler. Section 6.2.1, Using Fusion Middleware Control to Configure Primary and Secondary Instances Verify that the new components are available. Section 5.6.1, Using Fusion Middleware Control to View System Component Availability Deploying Oracle Business Intelligence for High Availability 6-5

6.2.1 Using Fusion Middleware Control to Configure Primary and Secondary Instances

You can use Fusion Middleware Control to configure primary and secondary instances of the Cluster Controller and Oracle BI Scheduler. Figure 6–2 shows the Availability tab of the Capacity Management page. Figure 6–2 Availability Tab of Capacity Management Page in Fusion Middleware Control Before you begin this procedure, ensure that you are familiar with the information in Section 3.2, Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings. To configure primary and secondary instances of the Cluster Controller and Oracle BI Scheduler: 1. Go to the Business Intelligence Overview page, as described in Section 2.2.2, Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components. 2. Display the Availability tab of the Capacity Management page. On this page, you can configure primary and secondary instances of the Cluster Controller and Oracle BI Scheduler. Click the Help button on the page to access the page-level help for its elements. 3. Click Lock and Edit Configuration to allow changes to be made.