summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorSeshu Kumar M <seshu.kumar.m@huawei.com>2017-11-06 08:06:42 +0000
committerGerrit Code Review <gerrit@onap.org>2017-11-06 08:06:42 +0000
commit0d9914be6201a7fde13e0022e42ca7edd4cb55ef (patch)
tree6c6d456f406d8dcfa5c35e77a5cb9b458e03d51a /docs
parent91112ebf9aa2f5bcb66a4cba37943dc8318908a8 (diff)
parent03d5d1c68459fc4f05cd0ff386332fe355a0ceef (diff)
Merge "BPMN deployment strategy .rst file"
Diffstat (limited to 'docs')
-rw-r--r--docs/BPMN_Project_Deployment_Strategy.rst35
1 files changed, 35 insertions, 0 deletions
diff --git a/docs/BPMN_Project_Deployment_Strategy.rst b/docs/BPMN_Project_Deployment_Strategy.rst
new file mode 100644
index 0000000000..50f48363ed
--- /dev/null
+++ b/docs/BPMN_Project_Deployment_Strategy.rst
@@ -0,0 +1,35 @@
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.
+.. http://creativecommons.org/licenses/by/4.0
+.. Copyright 2017 Huawei Technologies Co., Ltd.
+
+BPMN Project Deployment Strategy
+==================================
+
+Single Application with Embedded Process Engine
+------------------------------------------------
+
+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:
+
+ * BPMN process flows, java classes, groovy scripts, and resource files from MSOInfrastructureBPMN itself.
+
+ * BPMN process flows, java classes, groovy scripts, and resource files from other SO projects, like MSOCommonBPMN and MSOCoreBPMN.
+
+ * An embedded Camunda Process Engine to execute the flows.
+
+The process application exposes a REST endpoint to the API Handler(s) for receiving flow execution requests.
+
+Development is required in SO to be able to support one a more versatile deployment strategy, probably one of the following:
+
+Shared Process Engine
+----------------------
+
+The Camunda Process Engine is created and manged as a Wildfly module. This single engine is shared by all process applications.
+
+Multiple Applications, each with an Embedded Process Engine
+-------------------------------------------------------------
+
+More than one application could be deployed, each having its own embedded process engine.
+
+
+
+