E-mail
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. |
|
| 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 (the outside client is responsible of the identifier uniqueness) 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. |
|
| Process step identifier | It is a GUUID (Global Universal Unique Identifier) identifying the current step in the current process instance. Inside Petals ESB, this identifier is automatically generated. |
|
| Process previous step identifier | It is a GUUID (Global Universal Unique Identifier) identifying the previous step of current step in the current process instance. Inside Petals ESB, this identifier is automatically transmitted step by step from the process step id of the previous step. Used in combination with the process previous step, it permits to rebuild the whole execution of process instance including loop and branch. |
|
| Component name | A component name is an unique name assigned to the component instance at installation time. |
|
| 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. |
|
| Log level | All log traces have a level indicating their severity. The logging system can be configured to filter traces to log against their severity (see Logging in Petals). |
 | Global terms utilization This previous terms are not only used for BPEL |