Execution Profile
When deploying a model, the possibility to choose an execution profile allows the user to determine the level of events when a service is running.
These events are sent to emitters that are registered on the service topic.
Three profiles are available, sorted based on the amount of information emitted:
-
Production
-
Audit
-
Debug
The main difference between those profiles is the number of messages emitted and the content of the messages. Each profile adds more information on top of the less detailed one.
Information about messages structure is available in the Event Definition documentation.
BPMN Modeler Specific
Production
Within that profile, four messages are emitted:
| Type | Definition |
|---|---|
ServiceStarted |
A service started to run. |
ServiceFinished |
A service finished to run. |
ServiceSuspended |
A service has been suspended and is in a wait state. |
ServiceResumed |
A service has been resumed. |
Audit/Debug
Within those profiles, all messages emitted with the Production profile will also be emitted when a service runs, plus messages related to nodes lifecycle and data will be emitted.
| Type | Definition |
|---|---|
ServiceNodeStarted |
A node has been triggered. |
ServiceNodeFinished |
A node has been left. |
ServiceDataChanged |
A variable inside the service has been updated. |
The only difference between Audit and Debug profiles is about the payload’s content. Those differences are described as well in the Event Definition documentation. When a field is set to be available in a specific profile only, it is mentioned through brackets. Also, if a field is specific to a type of node, information is also placed between brackets.
A ServiceDataChanged message will also be emitted when a variable is updated while a service is running. The content of the message will not differ between the Audit and Debug profile.