VulCon first flow - Revision history

Anonymous: /* First flow service */

2012-04-18T21:09:01Z

‎First flow service

Anonymous: /* First flow service */

2012-03-05T13:20:36Z

‎First flow service

Anonymous at 13:18, 5 March 2012

2012-03-05T13:18:56Z

Anonymous at 17:15, 10 February 2012

2012-02-10T17:15:22Z

Anonymous: /* First flow service */

2012-02-10T17:01:01Z

‎First flow service

Anonymous at 13:50, 10 February 2012

2012-02-10T13:50:42Z

Anonymous at 13:49, 10 February 2012

2012-02-10T13:49:46Z

Anonymous at 11:36, 10 February 2012

2012-02-10T11:36:29Z

Anonymous at 11:30, 10 February 2012

2012-02-10T11:30:03Z

Anonymous at 11:13, 10 February 2012

2012-02-10T11:13:00Z

@@ Line 21: / Line 21: @@
 *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. Once a service flow is correctly configured, the user can export its configuration from [[{{VULCON}} deploy]] and test {{L_GVCONSOLE}}.
+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
 More examples are available [[First projects|here]].

@@ Line 16: / Line 16: @@
 *[[Channel]]
 *[[Operation]]
-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:
+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

@@ Line 16: / Line 16: @@
 *[[Channel]]
 *[[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. 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:
+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 nome.
+*id: add the node name.
 *on-critical-error: error management, you decide whether to continue or end the flow
-*next-node-id: the next node
+*next-node-id: name of the next node
-*output: GVBuffer naming the output node
+*output: [[GVBuffer]] naming the output node
 after the operation the new node will be configured and displayed on the flow. Once a service flow is correctly configured, the user can export its configuration from [[{{VULCON}} deploy]] and test {{L_GVCONSOLE}}.

@@ Line 6: / Line 6: @@
 </syntaxhighlight>
 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
 [[File:OperationDiagram.png|thumb|Operation diagram]]

@@ Line 5: / Line 5: @@
 GVServices --> Services
 </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]]
 *[[Synchronous  - Asynchronous]]

← Older revision		Revision as of 11:36, 10 February 2012
Line 20:		Line 20:
	*next-node-id: the next node		*next-node-id: the next node
	*output: GVBuffer naming the output node		*output: GVBuffer naming the output node
		+	after the operation the new node will be configured and displayed on the flow