Oracle Business Activity Monitoring Configuration Artifacts

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-77 separate both components. The Oracle WebLogic Administration Console allows starting and stopping Oracle BAM. This can also be done using WLST commands. Oracle Enterprise Manager Fusion Middleware Control Console allows multiple operations and configuration of the BAM Web Applications. Figure 5–35 Oracle Enterprise Manager Fusion Middleware Control

5.11.1.4 Oracle Business Activity Monitoring Configuration Artifacts

Oracle Enterprise Manager Fusion Middleware Control exposes some of the configuration options for Oracle BAM Server. Figure 5–36 Configuring Oracle Business Activity Monitoring The properties exposed by Oracle Enterprise Manager are a mix of the information contained in two different files: BAMServerConfig.xml and Note: Although Enterprise Manager offers separate start and stop for Oracle BAM Server and Oracle BAM Web Applications, this is in reality a stop operations that affects both components, meaning if Oracle BAM Server is stopped from Enterprise Manager, the corresponding Oracle BAM Web Applications are also stopped, and the reverse is also true. This also applies for start operations. 5-78 Oracle Fusion Middleware High Availability Guide BAMCommonConfig.xml. These files are located under the DOMAIN_ HOME serversBAM_Server_Nametmp_WL_useroracle-bam_ 11.1.1yhryfpAPP-INFclassesconfig directory notice that yhryfp is the random directory generated at installation time for deploying BAM applications. This is the random directory generated at installation time for deploying Oracle BAM applications. The properties in these files are modifiable by using the Mbeans exposed in Oracle Enterprise Manager Fusion Middleware Control. For details on the configuration options for Oracle BAM Servers, refer to the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle Business Process Management Suite and the Oracle Fusion Middleware Users Guide for Oracle Business Activity Monitoring. Similarly, some properties are exposed for Oracle BAM Web Applications by Oracle Enterprise Manager Fusion Middleware Control as shown in Figure 5–37 . Figure 5–37 Oracle Business Activity Monitoring Configuration Properties Configuration options at the container level, such as data sources and persistent stores, are maintained as part of Oracle WebLogic Server Domain configuration and are synchronized across a cluster of Oracle WebLogic Servers by Oracle WebLogic Server core infrastructure. See the Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite for details on configuring Oracle BAM. 5.11.2 Oracle Business Activity Monitoring High Availability Architecture and Failover Considerations Figure 5–38 describes a two-node Oracle BAM cluster running on two Oracle WebLogic Servers. The Oracle WebLogic Servers are frontended by Oracle HTTP Servers which load balance incoming requests to them. The following are the main characteristics of this configuration: ■ Oracle BAM Web Applications run on two clustered WebLogic Server managed servers. The WebLogic Server Cluster synchronizes configuration for common artifacts of WebLogic Server used by Oracle BAM Web Applications, such as data sources, persistent store, and definitions. Oracle BAM Server is targeted by any of the servers where BAM Web applications are running. Only one WebLogic server runs Oracle BAM Server. ■ The architecture uses Oracle WebLogic Server Migration feature to protect Oracle WebLogic Server that runs both Oracle BAM Web Applications and Oracle BAM Server in BAMHOST1 against failures. This provides protection for Oracle BAM Server which is a singleton. The WebLogic Managed Server in which Oracle BAM Server runs is listening on a Virtual IP that gets migrated to another node when Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-79 the failover occurs. This is the address that Oracle BAM Web Applications in BAMHOST2 use to connect to an Oracle BAM Server. Plan appropriately to account for the scenario where Oracle BAM Server and two instances of Oracle BAM Web Applications are running on BAMHOST2. For more information on Server Migration features, see Chapter 3, High Availability for WebLogic Server. ■ Oracle BAM’s database is configured with Oracle Real Application Clusters Oracle RAC to protect from database failures. Oracle BAM Server performs the appropriate reconnection and operations retries if database instance failure occurs. Figure 5–38 Oracle BAM High Availability Architecture Internet Load Balancer BAMHOST1 BAMHOST2 WLS Cluster Firewall 1 Firewall 2 VIP0 WLS_BAM1 BAM Web Apps BAM Server Admin Server VIP1 WLS_BAM2 BAM Web Apps VIP WEBHOST2 OHS WEBHOST1 OHS RAC - BAM Server Migration Failover WLS_BAM1 BAM Web Apps BAM Server Admin Server Manual Failover 5-80 Oracle Fusion Middleware High Availability Guide

5.11.2.1 Oracle Business Activity Monitoring Protection from Failures and Expected Behavior