View Source

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 \\ ||
| * Process | Set of steps assembled to define a processing. \\ | |
| * Process identifier | Identifier associated to a process. \\ | * processId |
| * Process instance | When a process is invoked, a process instance is created representing the process execution. \\ | |
| * Process instance identifier | 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. \\ | * processInstanceId
* -correlationId-
* -processExecutionId-
* -processRequestId-
* -globalMessageId-
* -contextUuid- |
| * Process loop identifier | 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. \\ | * processLoopId |
| * Process branch identifier | 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. | * processBranchId
* -branchId- |
| * Component instance identifier | Key identifier associated to the component instance to identify uniquely a component instance inside a Petals node. It is used as logger name. \\ | * componentInstanceId
* -componentName-
* -loggerName- |
| * Trace code | A code identifying uniquely a trace type in log. For example, all service invocations are logged on the consumer side with the same code. \\ | * traceCode |

\\
{info:title=Global terms utilization}
This previous terms are not only used for BPEL
{info}