View Source

{section}
{column}
{multi-excerpt:name=features}

h1. Features

The component SE Activity provides two operational mode:
* integration mode, that exposes a service-based API of the engine Activity. Several services are provided by the component to interact directly with the engine Activity,
* service mode to implement your services using orchestrations and workflows.

h2. Integration mode

{color:red}*TODO*{color}

h2. Service mode

The mode "Service" of the SE Activity permits to implement your services using orchestration and/or process capabilities of Activity.

*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. As Activity supports BPMN2, it is possible to implement your orchestration as a process containing only service tasks:
{gliffy:name=activity_orchestration|align=center|border=false}


{color:red}*TODO*{color}



*Process & Orchestration*

The Activity Service-Engine allows to run process or service orchestration.

Each configuration of this component embeds an Activity process definition.
When such a configuration is deployed, a service with several operations is deployed providing following features:
* start a process instance of the process definition,
* complete the current task,
* retrieve process instances according to several criteria.

{tip}Available operations can be different from a version of the component to another version. See the user guide of the right version.{tip}

*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-Activity Documentations}{children:all=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list}{panel}
{column}
{section}