| seshukm | 03d5d1c | 2017-11-06 10:47:37 +0530 | [diff] [blame] | 1 | .. This work is licensed under a Creative Commons Attribution 4.0 International License. |
| 2 | .. http://creativecommons.org/licenses/by/4.0 |
| 3 | .. Copyright 2017 Huawei Technologies Co., Ltd. |
| 4 | |
| 5 | BPMN Project Deployment Strategy |
| 6 | ================================== |
| 7 | |
| 8 | Single Application with Embedded Process Engine |
| 9 | ------------------------------------------------ |
| 10 | |
| 11 | Deployment in SO is currently limited to a single process application: MSOInfrastructureBPMN. The WAR file for this application contains everything needed to execute the infrastructure process flows, including: |
| 12 | |
| 13 | * BPMN process flows, java classes, groovy scripts, and resource files from MSOInfrastructureBPMN itself. |
| 14 | |
| 15 | * BPMN process flows, java classes, groovy scripts, and resource files from other SO projects, like MSOCommonBPMN and MSOCoreBPMN. |
| 16 | |
| 17 | * An embedded Camunda Process Engine to execute the flows. |
| 18 | |
| 19 | The process application exposes a REST endpoint to the API Handler(s) for receiving flow execution requests. |
| 20 | |
| 21 | Development is required in SO to be able to support one a more versatile deployment strategy, probably one of the following: |
| 22 | |
| 23 | Shared Process Engine |
| 24 | ---------------------- |
| 25 | |
| 26 | The Camunda Process Engine is created and manged as a Wildfly module. This single engine is shared by all process applications. |
| 27 | |
| 28 | Multiple Applications, each with an Embedded Process Engine |
| 29 | ------------------------------------------------------------- |
| 30 | |
| 31 | More than one application could be deployed, each having its own embedded process engine. |
| 32 | |
| 33 | |
| 34 | |
| 35 | |