Difference between revisions of "Parallel Flow"
Line 1: | Line 1: | ||
The Iterations nodes are: | The Iterations nodes are: | ||
[[File:ParallelNode.png|thumb|{{GVESB}} Paraleel Nodes]] | [[File:ParallelNode.png|thumb|{{GVESB}} Paraleel Nodes]] | ||
− | *Spawn SubFlow: | + | *Spawn SubFlow: Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flow as spawned process. |
− | *Parallel SubFlow: . | + | *Parallel SubFlow: Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flows as parallel process. |
− | *Split SubFlow : | + | *Split SubFlow : Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flows as parallel process. |
=={{VULCON}} Configuration== | =={{VULCON}} Configuration== |
Revision as of 10:36, 15 May 2014
The Iterations nodes are:
- Spawn SubFlow: Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flow as spawned process.
- Parallel SubFlow: Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flows as parallel process.
- Split SubFlow : Node that allows direct invocation of a GreenVulcanoESB core workflow sub-flows as parallel process.
VulCon Configuration
You might insert into your workflow one of the Nodes described above by drag and drop it into the VulCon Editor View.
When one of these nodes is inserted into the editor, a new element GVIteratorOperationNode will appear into the element Flow (or SubFlow) of your Service Operation. This element will contain a sub-element which variates depending on the Iteration Node you selected. The following table shows this:
GVSubFlowSpawnNode | GVSubFlowSpawnNode Sub-element | Description |
---|---|---|
GVSubFlowParallelNode | GVSubFlowParallelNode | Sets a proxy to other Enqueue operation. |
{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>