Operation - Revision history

G.dimaio at 09:26, 13 May 2014

2014-05-13T09:26:50Z

G.dimaio at 09:25, 13 May 2014

2014-05-13T09:25:22Z

Anonymous: /* Description */

2012-02-27T11:58:50Z

‎Description

Anonymous at 12:06, 10 February 2012

2012-02-10T12:06:18Z

Anonymous at 12:05, 10 February 2012

2012-02-10T12:05:26Z

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-02T14:37:06Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: /* {{VULCON}} / {{GVCONSOLE}} Configuration */

2012-02-02T14:35:42Z

‎{{VULCON}} / {{GVCONSOLE}} Configuration

Anonymous: Created page with "==Description== {{GVESB}} uses the element ''Operation'' to define an operational workflow. Each workflow is identified by a triple and it ..."

2012-02-02T14:23:51Z

Created page with "==Description== {{GVESB}} uses the element ''Operation'' to define an operational workflow. Each workflow is identified by a triple <service, client, operation> and it ..."

New page

==Description==

{{GVESB}} uses the element ''Operation'' to define an operational workflow.

Each workflow is identified by a triple <[[service]], [[client]], operation> and it is made instantiating a [[Flow]], with VCL operations ({{GVESB}} [[plugins]]) of one or more participating systems ([[Participant]] selected from those defined in the [[System|Systems]]).

=={{VULCON}} / {{GVCONSOLE}} Configuration==

{{GVESB}} allows you to configure the following operations:
* Forward
* GetReply
* GetRequest
* Request
* RequestReply
* SendReply

And correspond (apart from the Forward) to the communication primitives of {{GVESB}}.

The Forward workflows are driven by the internal mechanisms of {{GVESB}} to complete transactions that do not require assistance from external systems.

You can enable some consistency check on the data passed on {{GVESB}}.

The Operation Element is used by [[Client]] and its attributes are:
* ''type'': operation.
* ''name'': Operation's name. Corresponds to a {{GVESB}} communication primitive or a forward. <br/> In the case of a forward, then you must also specify the parameter ''forward-name''. The attribute's admitted values are:
** RequestReply
** Request
** GetReply
** GetRequest
** SendReply
** Forward
* ''forward-name'': Forward's name. Must be specified only if you are setting up a workflow for a forward.
* ''out-check-type'': Enable a consistency check of GVBuffer. It can take three values:
** none: does not make any check.
** sys-svc: fields [[system]] and [[service]] the result should take the same values in the input buffer.
** sys-svc-id: fields [[system]], [[service]] and ''id'' of the result must assume the same values that assumed in the input
buffer. <br/> This setting should not be used in transactions with semantics ''GetRequest''. The attribute's admitted values are:
* ''operation-activation'': Activation status of the current [[system]]/[[service]] operation. The state can take two values:
** on: the operation is active. Default value.
** off: the operation is not active.

''Operation'' has the following subelements:
* Description
* [[Participant]]
* [[Flow]]
* [[SubFlow]]
* [[OperationManagement]]

@@ Line 44: / Line 44: @@
   - none: does not make any check.
   - sys-svc: fields [[system]] and [[service]] the result should take the same values in the input buffer.
-  - sys-svc-id: fields [[system]], [[service]] and ''id'' of the result must assume the same values that assumed in the input buffer. This setting should not be used in operations with semantics ''GetRequest''.
+  - sys-svc-id: fields [[system]], [[service]] and ''id'' of the result must assume the same values that assumed in the input buffer.<br/>This setting should not be used in operations with semantics ''GetRequest''.
 |-
 | operation-activation || required || Activation status of the current [[system]]/[[service]] operation. The state can take two values:

@@ Line 12: / Line 12: @@
 * GetRequest
 * Request
-* RequestReply : is one of the basic methods system use to talk to each other. When using request-response, the first system requests some data and the second computer responds to the request. Usually there is a series of such interchanges until the complete message is sent
+* RequestReply
 * SendReply
@@ Line 21: / Line 21: @@
 You can enable some consistency check on the data passed on {{GVESB}}.
-The Operation Element is used by [[Client]] and its attributes are:
+The Operation Element is used by [[Service]] and its attributes are:
-* ''type'': operation.
+{|class="gvtable"
-* ''name'': Operation's name. Corresponds to a {{GVESB}} communication primitive or a forward. <br/> In the case of a forward, then you must also specify the parameter ''forward-name''. The attribute's admitted values are:
+! Attribute !! Type !! Description
-** RequestReply:
+|-
-** Request
+| class || fixed || This attributes must assume the value '''it.greenvulcano.gvesb.core.flow.GVFlowWF'''
-** GetReply
+|-
-** GetRequest
+| type || fixed || This attributes must assume the value '''operation'''
-** SendReply
+|-
-** Forward
+| name || required || Operation's name. Corresponds to a {{GVESB}} communication primitive or a forward.
-* ''forward-name'': Forward's name. Must be specified only if you are setting up a workflow for a forward.
-* ''out-check-type'': Enable a consistency check of GVBuffer. It can take three values:
+The attribute's admitted values are:
-** none: does not make any check.
+ - RequestReply
-** sys-svc: fields [[system]] and [[service]] the result should take the same values in the input buffer.
+ - Request
-** sys-svc-id: fields [[system]], [[service]] and ''id'' of the result must assume the same values that assumed in the input
+ - GetReply
-buffer. <br/> This setting should not be used in transactions with semantics ''GetRequest''. The attribute's admitted values are:
+ - GetRequest
-* ''operation-activation'': Activation status of the current [[system]]/[[service]] operation. The state can take two values:
+ - SendReply
-** on: the operation is active. Default value.
+ - Forward
-** off: the operation is not active.
+|-
 ''Operation'' has the following subelements:
@@ Line 45: / Line 57: @@
 * [[Flow]]
 * [[SubFlow]]
-* [[conditions]]
+* [[Conditions]]
 * OperationManagement

@@ Line 3: / Line 3: @@
 {{GVESB}} uses the element ''Operation'' to define an operational workflow.
-Each workflow is identified by a triple <[[service]], [[client]], operation> and it is made instantiating a [[Flow]], with VCL operations ({{GVESB}} [[plugins]]) of one or more participating systems ([[Participant]] selected from those defined in the [[System|Systems]]).
+Each workflow is identified by a triple <[[service]], [[client]], [[operation]]> and it is made instantiating a [[Flow]], with VCL operations ({{GVESB}} [[plugins]]) of one or more participating systems ([[Participant]] selected from those defined in the [[System|Systems]]).
 =={{VULCON}} / {{GVCONSOLE}} Configuration==