Difference between revisions of "VulCon first flow"

From GreenVulcano Wiki
Jump to: navigation, search
(First flow service)
 
(8 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
GVServices --> Services
 
GVServices --> Services
 
</syntaxhighlight>
 
</syntaxhighlight>
and clicking on the Services element with the right mouse button, as shown in the figure, the user can choose four different types of services:
+
and clicking on the Services element with the right mouse button, as shown in the figure, the user can choose four different [[Paradigms of communication]]:
*[[Synchronous  - Synchronous]]
+
*[[Paradigms_of_communication#Synchronous-Synchronous|Synchronous  - Synchronous]]
*[[Synchronous  - Asynchronous]]
+
*[[Paradigms_of_communication#Synchronous-Asynchronous|Synchronous  - Asynchronous]]
*[[Asynchronous - Synchronous ]]
+
*[[Paradigms_of_communication#Asynchronous-Synchronous|Asynchronous - Synchronous ]]
*[[Asynchronous - Asynchronous]]
+
*[[Paradigms_of_communication#Asynchronous-Asynchronous|Asynchronous - Asynchronous]]
 +
 
 
In addition to service name, user may select a group (among those ones already configured) and a communication paradigm between the couples Client-ESB and ESB-Server. Now let’s choose “DEFAULT_GRP” as group and “Synchronous-Synchronous” as scenario. Service will be called “TOUPPER_VULCON”. Continuing with the wizard the user chooses the triple
 
In addition to service name, user may select a group (among those ones already configured) and a communication paradigm between the couples Client-ESB and ESB-Server. Now let’s choose “DEFAULT_GRP” as group and “Synchronous-Synchronous” as scenario. Service will be called “TOUPPER_VULCON”. Continuing with the wizard the user chooses the triple
 
[[File:OperationDiagram.png|thumb|Operation diagram]]
 
[[File:OperationDiagram.png|thumb|Operation diagram]]
Line 15: Line 16:
 
*[[Channel]]
 
*[[Channel]]
 
*[[Operation]]
 
*[[Operation]]
After clicking on finish button, a new TOUPPER_VULCON service will be available,and the editor displays the flow {{VULCON}},see figure Operation diagram.
+
After clicking on finish button, a new TOUPPER_VULCON service will be available, and the {{VULCON}} editor will display the flow, see figure Operation diagram. User may customize a service flow, adding new operation nodes with the [[Palette]] tool. For example, let’s add a [[GVNotificationNode|Notification node]] to notify a flow error (after the check node: it’s identified with a red arrow). When you drag the Node Editor on the new Notification Wizard will appear, to guide the user to the configuration of the node in this case the necessary steps are:
 
+
*id: add the node name.
 
+
*on-critical-error: error management, you decide whether to continue or end the flow
 
+
*next-node-id: name of the next node
 
+
*output: [[GVBuffer]] naming the output node
 
+
after the operation the new node will be configured and displayed on the flow.If the User wants to reconfigure a node, it can make or
 
+
propertis through the voice, or just double click on its node to log back into the configuration wizard.Once a service flow is correctly configured, the user can export its configuration from [[{{VULCON}} deploy]] and test {{L_GVCONSOLE}}.
 
 
  
'''da eliminare'''
+
More examples are available [[First projects|here]].
The easiest way to create a [[{{VULCON}} Service]] is interacting with the “Wizard New Service” option. From the Core view, select the wizard item in the drop down menu shown expanding the GVServices element and clicking on the Services element with the right mouse button. In addition to service name, user may select a group (among those ones already configured) and a communication paradigm between the couples Client-ESB and ESB-Server. In this new service, client will be any system suggested with {{GVESB}} name, and server will be an internal {{GVESB}} test service.
 

Latest revision as of 21:09, 18 April 2012

First flow service

Wizard New Service

The easiest way to create a VulCon service is interacting with the “Wizard New Service” option. From the Core view

GVServices --> Services

and clicking on the Services element with the right mouse button, as shown in the figure, the user can choose four different Paradigms of communication:

In addition to service name, user may select a group (among those ones already configured) and a communication paradigm between the couples Client-ESB and ESB-Server. Now let’s choose “DEFAULT_GRP” as group and “Synchronous-Synchronous” as scenario. Service will be called “TOUPPER_VULCON”. Continuing with the wizard the user chooses the triple

Operation diagram

After clicking on finish button, a new TOUPPER_VULCON service will be available, and the VulCon editor will display the flow, see figure Operation diagram. User may customize a service flow, adding new operation nodes with the Palette tool. For example, let’s add a Notification node to notify a flow error (after the check node: it’s identified with a red arrow). When you drag the Node Editor on the new Notification Wizard will appear, to guide the user to the configuration of the node in this case the necessary steps are:

  • id: add the node name.
  • on-critical-error: error management, you decide whether to continue or end the flow
  • next-node-id: name of the next node
  • output: GVBuffer naming the output node

after the operation the new node will be configured and displayed on the flow.If the User wants to reconfigure a node, it can make or propertis through the voice, or just double click on its node to log back into the configuration wizard.Once a service flow is correctly configured, the user can export its configuration from VulCon deploy and test GV Console®.

More examples are available here.