Oracle Business Process Web Applications Single Instance Characteristics

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

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

5.4.3.1 Oracle Business Process Web Applications Single Instance Characteristics

This section provides single instance information for Oracle Business Process web applications.

5.4.3.1.1 Oracle Business Process Web Applications Single Instance Architecture

Figure 5–22 shows Oracle BPM Suite web applications and their interactions with other BPMN components. Figure 5–22 Oracle BPM Suite Web Applications The web applications are stateless. The state is maintained in the Dehydration Service and the data is exposed through the Operational APIs or in MDS.

5.4.3.1.2 Oracle Business Process Web Applications External Dependencies Both BPM

Workspace and BPM Composer are deployed separately from the BPMN Service Engine, but depend on it completely. If the BPMN Service Engine is stopped soa-infra system, neither BPM Workspace nor BPM Composer will be able to access information and metadata about deployed projects. Given the dependency of soa-infra on the SOA MDS database, by extension the Business Process web applications depend on the MDS database to be available. Web Applications: Process Workspace: Perform, Organize, Manage Work MDS Metadata: Projects Templates Dehydration Store: Instance Info Process Cubes Identity Policy Store: Identity, Roles LDAP or other Directory Process Portal: Collaborative Group Spaces WebCenter Spaces Process Composer: Process Rules Customization BPM Server: Operational API’s Service Engines - BPMN, BPEL, Workflow, Rules, Mediator SOAInfrastructure - Service Infra, JCA Connectivity Infra, Security Policy Infra 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