E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (6)
View Page History
...
The following terms are defined in Petals ESB context and must be used in all technical and functional documents. * -contextUuid- |
| * Process loop identifier | This identifier is used to identify the loop iteration in which steps are executed. Without the process instance identifier, this identifier has no real sens. It can be initialized from outside client when entering in Petals ESB and transmitted to application resources. \\
| * Process loop identifier | This identifier is used to identify the loop iteration in which steps are executed. Without the process instance identifier, this identifier has no real sens. It can be initialized from outside client when entering in Petals ESB and transmitted to application resources. \\
This identifier is formed as: <main-loop-id>\[glossary:-<sub-loop-id>\] where: \\
* <main-loop-id> is the process loop identifier of the first process step. It is defined as '0' if no value was provided by a outside client,
* <sub-loop-id> is defined as: <iteration-number>\[glossary:-<sub-loop-id>\] where <iteration-number> is the loop iteration number starting to 0. <sub-loop-id> will identify sub-loop iterations of the current loop. | * processLoopId |
| * Process branch identifier | This identifier is used to identify the parallel branch in which steps are executed. Without the process instance identifier, this identifier has no real sens. It can be initialized from outside client when entering in Petals ESB and transmitted to application resources. \\
This identifier is formed as: <main-branch-id>\[glossary:-<sub-branch-id>\] where: \\
* <main-branch-id> is the process branch identifier of the process main branch. It is defined as '0' if no value was provided by a outside client,
* <sub-branch-id> is defined as: <branch-id>\[glossary:-<sub-branch-id>\] where <branch-id> is a number starting to 0 and incremented by each created branch. <sub-branch-id> will identify a sub-branch of the current 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 |
| * 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]). 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 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.
...{petalslink:type=TODO Add terms}* Petals topology,
* Petals node (= \[glossary:JBI\] container),
* Petals network (= Petals topology instance),
* Petals domain,
* Petals domain,
...