The following terms are defined in Petals ESB context and must be used in all technical and functional documents.
| Terms |
Definition | Variable names in source code |
|---|---|---|
|
Set of steps assembled to define a processing. |
|
|
Identifier associated to a process. |
|
|
When a process is invoked, a process instance is created representing the process execution. |
|
|
It is a GUUID (Global Universal Unique Identifier) identifying one and only one process instance. It can be initialized from outside client when entering in Petals ESB and transmitted to application resources to retrieve all steps of a global business process. Inside Petals ESB, this identifier is automatically transmitted step by step. |
|
|
This identifier is used to identify the loop iteration in which steps are executed. Without the process execution identifier, this identifier has no real sens. This identifier is formed as: <main-loop-id>[-<sub-loop-id>] where:
|
|
|
This identifier is used to identify the parallel branch in which steps are executed. Without the process execution identifier, this identifier has no real sens. This identifier is formed as: <main-branch-id>[-<sub-branch-id>] where:
|
|
|
A component name is an unique name assigned to the component instance at installation time. |
|
|
A code identifying uniquely a trace type in log. For example, all service invocations are logged on the consumer side with the same code. |
|
| Global terms utilization This previous terms are not only used for BPEL |
This identifier is formed as: <main-loop-id>[-<sub-loop-id>] where:
- <main-loop-id> is the process loop identifier of the process first step. It is defined as '0',
- <sub-loop-id> is defined as: <iteration-number>[-<sub-loop-id>] where <iteration number> is the loop iteration number starting to 0.