Difference between revisions of "Flow"

From GreenVulcano Wiki
Jump to: navigation, search
(Created page with "==Definition== A Flow is a sequence of nodes with the operations of one or more participating systems, Participant, selected from those defined in the Systems section. ...")
 
(How to)
Line 26: Line 26:
  
 
It can be also done using the {{VULCON}} editor, by dragging the node into, and associating it to the ''Start'' node using the [[Default connection]]. Once the editor will be saved, ''Flow'' attributes will filled automatically.
 
It can be also done using the {{VULCON}} editor, by dragging the node into, and associating it to the ''Start'' node using the [[Default connection]]. Once the editor will be saved, ''Flow'' attributes will filled automatically.
 +
 +
 +
The respective part of the configuration file ''GVCore.xml'' become:
 +
 +
<syntaxhighlight lang="XML">
 +
<Service group-name="DEFAULT_GRP" id-service="TOUPPER#GVESB" service-activation="on" statistics="off">
 +
    <Operation name="RequestReply" operation-activation="on" out-check-type="sys-svc-id" type="operation">
 +
        <Participant id-channel="TEST_CHANNEL" id-system="GVESB"/>
 +
        <Flow first-node="test" point-x="20" point-y="150">
 +
            <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
 +
                  id="test" id-system="GVESB" input="input" next-node-id="end" op-type="call"
 +
                  operation-name="toupper_call" output="output" point-x="186" point-y="152" type="flow-node"/>
 +
            <GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode" end-business-process="yes" id="end" op-type="end"
 +
                  output="output" point-x="386" point-y="150" type="flow-node"/>
 +
        </Flow>
 +
    </Operation>
 +
</Service>
 +
</syntaxhighlight>

Revision as of 18:17, 26 January 2012

Definition

A Flow is a sequence of nodes with the operations of one or more participating systems, Participant, selected from those defined in the Systems section.

VulCon / GreenVulcano® ESB Configuration

Flow element

For each triple Client-Service-Operation a flow will be instantiated. This element defines a 'flow' to implement a GreenVulcano® ESB primitive communication with a workflow actually executable.

Using the sub-element Conditions can be (re)defined the conditions for possible use in the workflow routing.

It has the following attributes:

  • first-node: Indicates the initial node of the workflow.
    From this node begins running when a workflow instance is invoked.
  • point-x: X position of the start node in the VulCon® workflows editor.
  • point-y: Y position of the start node in the VulCon workflows editor.

and the subelements:


How to

Flow attributes

The flow element appears automatically when an Operation is created. For setting the attribute first-node it you must add your first node. It can be made from the Core view by right clicking the Flow element, Insert after (or Insert before), and selecting one of the available nodes.

It can be also done using the VulCon editor, by dragging the node into, and associating it to the Start node using the Default connection. Once the editor will be saved, Flow attributes will filled automatically.


The respective part of the configuration file GVCore.xml become:

<Service group-name="DEFAULT_GRP" id-service="TOUPPER#GVESB" service-activation="on" statistics="off">
    <Operation name="RequestReply" operation-activation="on" out-check-type="sys-svc-id" type="operation">
        <Participant id-channel="TEST_CHANNEL" id-system="GVESB"/>
        <Flow first-node="test" point-x="20" point-y="150">
             <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
                  id="test" id-system="GVESB" input="input" next-node-id="end" op-type="call"
                  operation-name="toupper_call" output="output" point-x="186" point-y="152" type="flow-node"/>
             <GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode" end-business-process="yes" id="end" op-type="end"
                  output="output" point-x="386" point-y="150" type="flow-node"/>
        </Flow>
    </Operation>
</Service>