Difference between revisions of "Routed-dequeue"
(Created page with "==Description== Used to make a routing mechanism at the level of communication channel, based on some conditions applied to the buffer GVBuffer. =={{VULCON}} / {{CONSOLE}} Conf...") |
(→{{VULCON}} / {{GVCONSOLE}} Configuration) |
||
(2 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
Used to make a routing mechanism at the level of communication channel, based on some conditions applied to the buffer GVBuffer. | Used to make a routing mechanism at the level of communication channel, based on some conditions applied to the buffer GVBuffer. | ||
− | =={{VULCON}} / {{ | + | =={{VULCON}} / {{GVCONSOLE}} Configuration== |
During the execution of flows, the operation is seen as a simple dequeue. | During the execution of flows, the operation is seen as a simple dequeue. | ||
Line 15: | Line 15: | ||
The routed-dequeue Element is used by [[Channel]] and [[routed-dequeue]]. Its attributes are: | The routed-dequeue Element is used by [[Channel]] and [[routed-dequeue]]. Its attributes are: | ||
− | + | {|class="gvtable" | |
− | + | ! Attribute !! Type !! Description | |
− | + | |- | |
+ | | type || fixed || This attribute must assume the value '''dequeue'''. | ||
+ | |- | ||
+ | | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.RoutedDequeue'''. | ||
+ | |- | ||
+ | | name || optional || Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations. | ||
+ | |} | ||
− | + | Might contain the following sub-elements: | |
* Description | * Description | ||
− | * GVBufferCondition | + | * [[GVBufferCondition]] |
− | * [[jms-dequeue]] or | + | * [[jms-dequeue]] or '''routed-dequeue''' |
* [[VCLRouting]] | * [[VCLRouting]] | ||
* [[ServiceAlias]] | * [[ServiceAlias]] |
Latest revision as of 13:28, 5 March 2012
Description
Used to make a routing mechanism at the level of communication channel, based on some conditions applied to the buffer GVBuffer.
VulCon / GV Console Configuration
During the execution of flows, the operation is seen as a simple dequeue.
The implementation of the routed-dequeue check the conditions and invokes a sub-operations accordingly.
To configure a routed-dequeue is necessary:
- defines sub-operations: Each sub operation is identified by a unique name within the routed-dequeue. The sub-operation can be selected are only those of type "dequeue".
- defines routing conditions: Check the values in GVBuffer fields. Each routing condition has a unique name within the routed-dequeue.
- associate routing conditions to operations: Sub items 'VCLRouting' associate routing conditions with operations. The evaluation order is defined by the order of items 'VCLRouting'. The sub-operation is performed corresponding to the first condition verified.
The routed-dequeue Element is used by Channel and routed-dequeue. Its attributes are:
Attribute | Type | Description |
---|---|---|
type | fixed | This attribute must assume the value dequeue. |
class | fixed | This attribute must assume the value it.greenvulcano.gvesb.virtual.RoutedDequeue. |
name | optional | Operation name. Used in the 'Flow' section to associate workflow nodes to VCL operations. |
Might contain the following sub-elements:
- Description
- GVBufferCondition
- jms-dequeue or routed-dequeue
- VCLRouting
- ServiceAlias