Operation

From GreenVulcano Wiki
Revision as of 14:23, 2 February 2012 by Anonymous (talk) (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 ...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Description

GreenVulcano® ESB 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 (GreenVulcano® ESB plugins) of one or more participating systems (Participant selected from those defined in the Systems).


VulCon / GV Console Configuration

GreenVulcano® ESB allows you to configure the following operations:

  • Forward
  • GetReply
  • GetRequest
  • Request
  • RequestReply
  • SendReply

And correspond (apart from the Forward) to the communication primitives of GreenVulcano® ESB.

The Forward workflows are driven by the internal mechanisms of GreenVulcano® ESB to complete transactions that do not require assistance from external systems.

You can enable some consistency check on the data passed on GreenVulcano® ESB.

The Operation Element is used by Client and its attributes are:

  • type: operation.
  • name: Operation's name. Corresponds to a GreenVulcano® ESB communication primitive or a forward.
    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.
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: