Difference between revisions of "Operations"
(→{{VULCON}} Configuration) |
|||
Line 29: | Line 29: | ||
| CoreCall || [[GVCoreCallNode]] || Allows direct invocation of a {{GVESB}} core workflow. | | CoreCall || [[GVCoreCallNode]] || Allows direct invocation of a {{GVESB}} core workflow. | ||
|- | |- | ||
− | | SubFlowCall || GVSubFlowCallNode || Allows direct invocation of a {{GVESB}} core workflow sub-flow. | + | | SubFlowCall || [[GVSubFlowCallNode]] || Allows direct invocation of a {{GVESB}} core workflow sub-flow. |
|} | |} | ||
{{VOTE}} | {{VOTE}} |
Revision as of 11:14, 5 March 2012
The Operation nodes are:
- Enqueue Node: Allows you to perform a queuing/publish on a queue/topic (defined in the systems).
- Dequeue Node: Allows you to perform a read from a queue or a topic (defined in section systems).
- Call Node: Allows you to perform a synchronous operation (defined in the systems).
- CoreCall Node: Allows you to make a call to another service GreenVulcano® ESB.
- SubFlowCall Node: Creates a sub-editor, to manage another flow.
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 a node is inserted into the editor, a new element will appear into the element Flow (or SubFlow) of your Service Operation depending on the node you selected. The following table shows this:
Operation node | GVCore element | Notes |
---|---|---|
Enqueue | GVOperationNode | Allows to perform a communication with an external systems (invocation, sending messages, receiving messages).
Its op-type parameter will be setted to enqueue |
Dequeue | GVOperationNode | Its op-type parameter will be setted to dequeue |
Call | GVOperationNode | Its op-type parameter will be setted to call |
CoreCall | GVCoreCallNode | Allows direct invocation of a GreenVulcano® ESB core workflow. |
SubFlowCall | GVSubFlowCallNode | Allows direct invocation of a GreenVulcano® ESB core workflow sub-flow. |
{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>