Oracle Business Activity Monitoring StartupShutdown Lifecycle Oracle Business Activity Monitoring Startup and Shutdown of Processes

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-75 Oracle BAM server uses JMS intensively. However, all Oracle BAM JMS queues are internal and do not require to be configured in a high availability configuration. When failover occurs, the queues are recreated on the new active Oracle BAM instance. Oracle BAM Web Application Modules can run in full active-active mode connecting to the available Oracle BAM server. The information is retrieved using RMI protocol to access the EJBs that provide the information to remote consumers. Oracle BAM Web Applications are stateless, except for the Reports Server, which maintains a session ID for reports or users accessing the systems. This requires enabling session replication for the WebLogic Managed Server where Oracle BAM Web Applications run. The processing of work by the EJBs and threads in Oracle BAM is non transactional and does not require Oracle WebLogic Server special transaction logs configuration. At the same time, Oracle BAM uses the database intensively, therefore it is important that Oracle BAMs database access is prepared for failure in the database. This requires configuring multi data sources for Oracle BAM data source as described in Section 5.15, Configuring High Availability for Oracle BAM . For information about multi data source configuration with Oracle RAC and the MDS repository, see Section 4.1.2, Using Multi Data Sources with Oracle RAC. External Dependencies Oracle BAM engine system depends only on the Oracle BAM database which contains Oracle BAM schemas for Oracle BAM data and report metadata. The database must be available for Oracle BAM system to start and run properly.

5.11.1.2 Oracle Business Activity Monitoring StartupShutdown Lifecycle

As shown in Figure 5–32 , when the WebLogic Server is started, the Oracle BAM Server application is initialized. During startup, the Active Data Cache loads all the data from the repository. The Reports Cache is initialized with the data required for the available systems. The Event Engine starts analyzing the data and preparing notifications. Oracle BAM Web Applications are configured at boot time with an Oracle BAM Servers address. When Oracle BAM Web Applications are started, they connect to the Active Data Cache in Oracle BAM server and retrieve the corresponding viewsets through the Reports Server. Once initialization is done, the system is ready to receive data from clients and raise events and update reports dynamically. Figure 5–32 Oracle Business Activity Monitoring StartupShutdown Lifecycle Start BAM Server Initialize ADC Wait for data from clients channels Monitor Data and Raise Events Stream Data to Web Apps Start BAM Web Apps Connect to BAM Server Initialize Report Server Refresh View Sets 5-76 Oracle Fusion Middleware High Availability Guide

5.11.1.3 Oracle Business Activity Monitoring Startup and Shutdown of Processes

Oracle BAM Server is an application, oracle-bam, that operates independently from the rest of the SOA Service Infrastructure. It runs in the managed server where Oracle BAM is installed. It gets started by default with Oracle WebLogic Managed Server to which Oracle BAM is deployed. Use Oracle WebLogic Server Administration Console to verify Oracle BAM Servers status and to start and stop it. You can also use WebLogic Server WLST command line to control the application. Figure 5–33 Startup and Shutdown of Oracle Business Activity Monitoring using WebLogic Server Oracle Enterprise Manager Fusion Middleware Control allows multiple operations and configuration of the BAM Server as well as monitoring its status. For details about monitoring and controlling the Oracle BAM engine, Oracle Fusion Middleware Administrator’s Guide for Oracle SOA Suite. Figure 5–34 Startup and Shutdown of Oracle Business Activity Monitoring using Fusion Middleware Control The BAM Web Applications run collocated by default in the same managed server as BAM Server. for example, the BAM server and BAM Web Applications are part of the same deployment in WebLogic Server Administration Console. They cant be stopped and managed separately from BAM Server by default. It is possible though, as explained in later sections, to manipulate WebLogic Server application targeting to 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