Oracle Business Process Analytics Single Instance Characteristics

5-34 Oracle Fusion Middleware High Availability Guide

5.4.3.1.3 Oracle Business Process Web Applications Startup and Shutdown Lifecycle BPM

Workspace and BPM Composer are standard J2EE applications. They are started when the WebLogic Server where BPM has been deployed is started. They can be controlled from the WebLogic Server Administration Console and can be stopped with a forced shutdown or a graceful shutdown.

5.4.3.1.4 Oracle Business Process Web Applications Log Files The Workspace and

Composer web applications write to the SOA WebLogic Server log file and SOA WebLogic Server output. For the location of the server logs, refer to Section 5.2.1.6, Oracle SOA Service Infrastructure Log File Locations. Oracle Enterprise Manager Fusion Middleware Control can be used for diagnosing log file messages.

5.4.3.2 Oracle Business Process Web Applications High Availability Considerations

This section describes high availability considerations for Oracle Business Process web applications.

5.4.3.2.1 Oracle Business Process Web Applications High Availability Architecture and Failover

Considerations Both BPM Workspace and BPM Composer are stateless web applications. When the WebLogic Servers they reside on are deployed behind a load balancer or an HTTP Server, the front end devices route requests indistinctly to either node on which the applications are running. When a node failure occurs, requests are redirected to the other available WebLogic Server and work on the user interface can continue without interruptions.

5.4.3.2.2 Configuring Oracle Business Process Web Applications for High Availability For

detailed instructions on configuring high availability for Oracle Business Process web applications, refer to Section 5.13, Configuring High Availability for Oracle SOA Service Infrastructure and Component Service Engines. These web applications are clustered in a stateless cluster as part of the configuration for Oracle SOA Service infrastructure.

5.4.3.2.3 Cluster-Wide Configuration Changes for Oracle Business Process Web Applications

There are no specific configuration files for the web applications that reside locally on the file system for the servers. Some property files, like the Workspace property file, workspace.properties, are part of the OracleBPMWorkspace.ear file but do not include any instance-specific settings. They are deployed and available wherever Oracle BPM Workspace is deployed.

5.4.4 Oracle Business Process Analytics High Availability

This section provides single instance and high availability information for Oracle Business Process Analytics.

5.4.4.1 Oracle Business Process Analytics Single Instance Characteristics

The following section provides information about Oracle Business Process Analytics single instance characteristics.

5.4.4.1.1 Oracle Business Process Analytics Single Instance Architecture The Oracle BPM

Suite has built-in analytical capabilities for support of business-friendly process dashboards and real-time monitoring of business processes using Oracle Business Activity Monitoring BAM. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-35 Figure 5–23 shows the Oracle BPM Suite Analytical Infrastructure. Figure 5–23 Oracle BPM Suite Analytical Infrastructure From a technical perspective, the Oracle BPM Suite Analytical Infrastructure is used for the support of process analytics as follows: ■ Audit Persistence The BPMN service engine is continuously generating audit events comprised of activity runtime data. The data of those audit events is persisted in audit tables of the service engine dehydration store. The audit data is the source of all analytical data. ■ JMS Topic To de-couple process execution from the preparation and publishing of analytical data, a JMS topic configured as part of the SOA Service Infrastructure is used. ■ Cube Action MDB A message driven bean MDB is used to trigger aggregation and persistence of the analytical data to the BPM cube schema stored in the SOA Service Infrastructure database. ■ BAM Action MDB A message driven bean MDB is used to publish analytical data towards the BAM adapter installed as part of the SOA Service Infrastructure. ■ Process Persistence For the persistence of audit events and analytical data to the SOA Infrastructure database, the Oracle BPM Suite leverages the Java Persistence API JPA Infrastructure. The persistence unit is configured to use the JTA data source jdbcSOADataSource and the provider org.eclipse.persistence.jpa.PersistenceProvider. 5-36 Oracle Fusion Middleware High Availability Guide

5.4.4.1.2 Oracle Business Process Analytics External Dependencies The Oracle Business

Process Analytics libraries and components run as part of the BPMN Service Engine infrastructure. They rely heavily on the BPMN Service Engine artifacts queues, stores, and JDBC resources to function properly. As is the case for the service infrastructure, the SOA database must be available for the Analytics framework to work. Additionally, when feeding data to BAM, the required BAM system must be up and running to process the analytical information.

5.4.4.1.3 Oracle Business Process Analytics Startup and Shutdown Lifecycle Since Oracle

Business Process Analytics is part of the BPMN Service Engine, its lifecycle is the same as the BPMN Service Engine’s lifecycle.

5.4.4.1.4 Oracle Business Process Analytics Log Files The following loggers are available

for tracing of the Oracle Business Process Analytics components: ■ oracle.bpm.analytics.measurement ■ oracle.bpm.analytics.cube ■ oracle.bpm.analytics.bam To enable logging for one of the analytical components, set the log level to TRACE.

5.4.4.2 Oracle Business Process Analytics High Availability Considerations