Difference between revisions of "Operation"
(2 intermediate revisions by 2 users not shown) | |||
Line 3: | Line 3: | ||
{{GVESB}} uses the element ''Operation'' to define an operational workflow. | {{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== | =={{VULCON}} / {{GVCONSOLE}} Configuration== | ||
Line 13: | Line 12: | ||
* GetRequest | * GetRequest | ||
* Request | * Request | ||
− | * RequestReply | + | * RequestReply |
* SendReply | * SendReply | ||
Line 22: | Line 21: | ||
You can enable some consistency check on the data passed on {{GVESB}}. | You can enable some consistency check on the data passed on {{GVESB}}. | ||
− | The Operation Element is used by [[ | + | The Operation Element is used by [[Service]] and its attributes are: |
− | + | {|class="gvtable" | |
− | + | ! Attribute !! Type !! Description | |
− | + | |- | |
− | + | | class || fixed || This attributes must assume the value '''it.greenvulcano.gvesb.core.flow.GVFlowWF''' | |
− | + | |- | |
− | + | | type || fixed || This attributes must assume the value '''operation''' | |
− | + | |- | |
− | + | | name || required || Operation's name. Corresponds to a {{GVESB}} communication primitive or a forward. | |
− | + | ||
− | + | The attribute's admitted values are: | |
− | + | - RequestReply | |
− | + | - Request | |
− | + | - GetReply | |
− | buffer. <br/> This setting should not be used in | + | - GetRequest |
− | + | - SendReply | |
− | + | - Forward | |
− | + | |- | |
+ | | forward-name || optional || Forward's name. Must be specified only if you are setting up a workflow for a forward. | ||
+ | |- | ||
+ | | out-check-type || required || Enable a consistency check of GVBuffer. It can take one of 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 operations with semantics ''GetRequest''. | ||
+ | |- | ||
+ | | operation-activation || required || 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: | ''Operation'' has the following subelements: | ||
Line 46: | Line 57: | ||
* [[Flow]] | * [[Flow]] | ||
* [[SubFlow]] | * [[SubFlow]] | ||
− | * [[ | + | * [[Conditions]] |
* OperationManagement | * OperationManagement | ||
Latest revision as of 09:26, 13 May 2014
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 Service and its attributes are:
Attribute | Type | Description |
---|---|---|
class | fixed | This attributes must assume the value it.greenvulcano.gvesb.core.flow.GVFlowWF |
type | fixed | This attributes must assume the value operation |
name | required | Operation's name. Corresponds to a GreenVulcano® ESB communication primitive or a forward.
The attribute's admitted values are: - RequestReply - Request - GetReply - GetRequest - SendReply - Forward |
forward-name | optional | Forward's name. Must be specified only if you are setting up a workflow for a forward. |
out-check-type | required | Enable a consistency check of GVBuffer. It can take one of 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. |
operation-activation | required | 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
- Conditions
- OperationManagement
OperationManagement
Use this element to define actions for performing on the domain against the following events:
- FailureAction: useful to disable a component (ejb, mdb) against a configurable rate of errors.
- EnableAction: useful to enable a component (ejb, mdb) against the enabling of the operation or service.
- DisableAction: useful to disable a component (ejb, mdb) against the disabling of the operation or service.
It has the following subelements:
- Description,
- FailureAction with attributes:
- component: Specifies the name of the component to disable.
- max-failure-rate: Specifies the number of bankruptcies in the second for the given operation before disabling the component.
The errors relate to a single server, and then consider that there are N servers in the cluster.
- EnableAction with attribute:
- component: Specifies the name of the component to enable.
- DisableAction with its attribute:
- component: Specifies the name of the component to disable.