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. \\
This identifier is formed as: <main-loop-id>\[-<sub-loop-id>\] where: \\
* <main-loop-id> is the process loop identifier of the first process 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. | * 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. \\
This identifier is formed as: <main-branch-id>\[-<sub-branch-id>\] where: \\
* <main-branch-id> is the process branch identifier of the process main branch. It is defined as '0',
* <sub-branch-id> is defined as: <branch-id>\[-<sub-branch-id>\] where <branch-id> is a number starting to 0 and incremented by each created sub-branch. | * processBranchId
* -branchId- |
| * Component name | A *component name* is an unique name assigned to the component instance at installation time. \\ | * 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 |
| * 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 [petalsesbsnapshot:Logging in PETALS]). Available severity are: \\
* ERROR: An error occurs when the service can not be provided:
** In a Petals ESB container point of view, an error is something that stops the processing of an internal component. Consequently, the Petals ESB is stopped because it can assume its functions.
** In a component (BC/SE) point of view, an error is something that stops the processing of the SE or BC, but other components are always running correctly. Consequently, the component could be stopped.
** In a service (service-unit) point of view, an error is something that stops the processing of a service but other services deployed on the same component are correctly running. Consequently, the service could be stopped.
* WARNING: An error occurs when the service can not be provided. In a Petals ESB container point of view, an error is something that stops the processing of an internal component. Consequently, the Petals ESB is stopped because it can assume its functions.
* INFO
* CONFIG
* MONIT
* DEBUG | |
{petalslink:type=TODO Add terms}* Petals topology,
* Petals node (= \[JBI\] container),
* Petals network (= Petals topology instance),
* Petals domain,
* Petals sub-domain
* Distribution peer-to-peer
* Static topology,
* Dynamic topology
* Self discovery{petalslink}
\\
{info:title=Global terms utilization}
This previous terms are not only used for BPEL
{info}
|| 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. \\
This identifier is formed as: <main-loop-id>\[-<sub-loop-id>\] where: \\
* <main-loop-id> is the process loop identifier of the first process 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. | * 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. \\
This identifier is formed as: <main-branch-id>\[-<sub-branch-id>\] where: \\
* <main-branch-id> is the process branch identifier of the process main branch. It is defined as '0',
* <sub-branch-id> is defined as: <branch-id>\[-<sub-branch-id>\] where <branch-id> is a number starting to 0 and incremented by each created sub-branch. | * processBranchId
* -branchId- |
| * Component name | A *component name* is an unique name assigned to the component instance at installation time. \\ | * 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 |
| * 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 [petalsesbsnapshot:Logging in PETALS]). Available severity are: \\
* ERROR: An error occurs when the service can not be provided:
** In a Petals ESB container point of view, an error is something that stops the processing of an internal component. Consequently, the Petals ESB is stopped because it can assume its functions.
** In a component (BC/SE) point of view, an error is something that stops the processing of the SE or BC, but other components are always running correctly. Consequently, the component could be stopped.
** In a service (service-unit) point of view, an error is something that stops the processing of a service but other services deployed on the same component are correctly running. Consequently, the service could be stopped.
* WARNING: An error occurs when the service can not be provided. In a Petals ESB container point of view, an error is something that stops the processing of an internal component. Consequently, the Petals ESB is stopped because it can assume its functions.
* INFO
* CONFIG
* MONIT
* DEBUG | |
{petalslink:type=TODO Add terms}* Petals topology,
* Petals node (= \[JBI\] container),
* Petals network (= Petals topology instance),
* Petals domain,
* Petals sub-domain
* Distribution peer-to-peer
* Static topology,
* Dynamic topology
* Self discovery{petalslink}
\\
{info:title=Global terms utilization}
This previous terms are not only used for BPEL
{info}