Oracle BPMN Service Engine High Availability Considerations

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-31 2. Start BPMN service engine. 3. BPM project composites are loaded from the MDS repository by the SOA Service Infrastructure. 4. BPMN components are dispatched to the BPMN service engine to be loaded. 5. The BPM project metadata, such as organization data and auditmeasurement metadata, is persisted in the infrastructure database. 6. Composite binding components are activated. 7. The BPMN engine services requests. 8. The shutdown signal is received by the SOA Service Infrastructure. 9. The SOA Service Infrastructure starts unloading composites. 10. Composite binding components are disabled. 11. BPMN components are dispatched to the BPMN engine to be unloaded. 12. The BPMN service engine shuts down.

5.4.2.1.4 Oracle BPMN Service Engine Log Files BPMN service engine loggers are set to

INFO by default. When trying to track down a message or instance, you may want to set the loggers to TRACE level to enable more output to the WebLogic Server log files. The BPMN service engine logs trace information to the same files as the SOA Service Infrastructure. For the location of the server logs, see Section 5.2.1.6, Oracle SOA Service Infrastructure Log File Locations.

5.4.2.2 Oracle BPMN Service Engine High Availability Considerations

This section guides you through the issues and considerations necessary for configuring Oracle BPMN Process Manager for high availability.

5.4.2.2.1 Oracle BPMN Service Engine High Availability Architecture and Failover

Considerations The BPMN service engine leverages the functionality of BPEL PM for process instance recovery. See Section 5.3.2.1, Oracle BPEL Process Manager Protection from Failures and Expected Behavior for more details on instance recovery. In Oracle Enterprise Manager Fusion Middleware Control, select BPMN Engine Service Engine for the administration of the BPMN service engine, as shown in Figure 5–20 . 5-32 Oracle Fusion Middleware High Availability Guide Figure 5–20 BPMN Service Engine Home Page in Enterprise Manager The home page of the BPMN service engine is comprised of several sub pages. The Dashboard page is the default page. For the recovery of BPMN service instances, select the Recovery tab, which opens the BPMN Service Engine Recovery page shown in Figure 5–21 . Figure 5–21 BPMN Service Recovery Page in Enterprise Manager

5.4.2.2.2 Configuring Oracle BPMN Service Engine for High Availability For detailed

instructions on configuring high availability for Oracle BPMN Service Engine, refer to Section 5.13, Configuring High Availability for Oracle SOA Service Infrastructure and Component Service Engines.

5.4.2.2.3 Cluster-Wide Configuration Changes for Oracle BPMN Service Engine The standard

Java EE artifacts that Oracle BPMN components use are configured as part of Oracle WebLogics domain in which SOA is installed. Oracle WebLogic Clusters provide automatic configuration synchronization for artifacts, such as data sources, persistent stores, and JMS modules across the WebLogic Server domain. At the same time, the Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-33 WebLogic Server cluster is in charge of synchronizing the deployments and libraries used by the Oracle BPMN components. As explained in Section 5.4.1.4, Oracle BPM Suite Configuration Artifacts, the Oracle BPMN components configuration is stored in the SOA MDS database. Changes are applied once per SOA server, but affect all Oracle BPMN instances in the same SOA domain.

5.4.3 Oracle Business Process Web Applications High Availability