{section}
{column}
{multi-excerpt:name=features}
h1. Features
The component SE BPMN includes a BPMN 2.0 engine and provides two operational mode:
* integration mode, that exposes a service-based API of a BPMN 2.0 engine,
* service mode to implement your services using orchestrations and workflows.
h2. Integration mode
The mode "Integration" of the SE BPMN2 permits to interact directly with the BPMN 2.0 engine through a service-based API. Several services are provided by the component to interact directly with the BPMN 2.0 engine. This mode is activated at the component level.
*Concurrency*
Several instance of the component can be deployed concurrently on Petals ESB. A sequence of service-based API invocations can be exploded on each component instances
h2. Service mode
The mode "Service" of the SE BPMN2 permits to implement your services using orchestration and/or process capabilities of BPMN 2.0. This mode is available through the deployment of a service unit including the process definition.
*Orchestration*
An orchestration is sequence of automatic service invocations, and can be modeled as a sequence of service tasks in a BPMN2 description. Creating an instance of such a process will start automatically the sequence of service invocations. With BPMN2 it is possible to implement your orchestration as a process containing only service tasks. For example, the following orchestration can be an implementation of a service processing a "New Order":
!orchestration-sample.png|align=center!
*Process*
A process or workflow can be "servicized" at different levels:
* when creating a new instance of the process definition,
* when completing a task of the process instance
* when searching process instances or tasks
For example, the previous sample can be reworked replacing two service tasks by human tasks with such a process:
!process-sample.png|align=center!
Then created services are:
* the service "New Order" associated to a process instance creation,
* the service "Order Prepared" associated to the completion of the task "prepareOrder",
* the service "Order Delivered" associated to the completion of the task "deliverOrder".
*Concurrency*
Several instance of the component can be deployed concurrently on Petals ESB. So, you are able to deploy each process definitions on several component instances to get high availability.
{multi-excerpt}
{column}
{column:width=25%}
{panel:title=Petals-SE-BPMN2 Documentations}{children:all=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}
{column}
{multi-excerpt:name=features}
h1. Features
The component SE BPMN includes a BPMN 2.0 engine and provides two operational mode:
* integration mode, that exposes a service-based API of a BPMN 2.0 engine,
* service mode to implement your services using orchestrations and workflows.
h2. Integration mode
The mode "Integration" of the SE BPMN2 permits to interact directly with the BPMN 2.0 engine through a service-based API. Several services are provided by the component to interact directly with the BPMN 2.0 engine. This mode is activated at the component level.
*Concurrency*
Several instance of the component can be deployed concurrently on Petals ESB. A sequence of service-based API invocations can be exploded on each component instances
h2. Service mode
The mode "Service" of the SE BPMN2 permits to implement your services using orchestration and/or process capabilities of BPMN 2.0. This mode is available through the deployment of a service unit including the process definition.
*Orchestration*
An orchestration is sequence of automatic service invocations, and can be modeled as a sequence of service tasks in a BPMN2 description. Creating an instance of such a process will start automatically the sequence of service invocations. With BPMN2 it is possible to implement your orchestration as a process containing only service tasks. For example, the following orchestration can be an implementation of a service processing a "New Order":
!orchestration-sample.png|align=center!
*Process*
A process or workflow can be "servicized" at different levels:
* when creating a new instance of the process definition,
* when completing a task of the process instance
* when searching process instances or tasks
For example, the previous sample can be reworked replacing two service tasks by human tasks with such a process:
!process-sample.png|align=center!
Then created services are:
* the service "New Order" associated to a process instance creation,
* the service "Order Prepared" associated to the completion of the task "prepareOrder",
* the service "Order Delivered" associated to the completion of the task "deliverOrder".
*Concurrency*
Several instance of the component can be deployed concurrently on Petals ESB. So, you are able to deploy each process definitions on several component instances to get high availability.
{multi-excerpt}
{column}
{column:width=25%}
{panel:title=Petals-SE-BPMN2 Documentations}{children:all=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}