E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History
...
The following terms are defined in Petals ESB context and must be used in all technical and functional documents. | * 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: \\
This identifier is formed as: <main-loop-id>\[-<sub-loop-id>\] where: \\
* <main-loop-id> is the process loop identifier of the process 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. \\
| * 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. \\
...* -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 |
| * 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 | |
* 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,
...{info:title=Global terms utilization}
This previous terms are not only used for BPEL
This previous terms are not only used for BPEL
{info}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.
* <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.
{info}