Difference between revisions of "GVOperationNode"

From GreenVulcano Wiki
Jump to: navigation, search
(Description)
({{VULCON}} / {{GVCONSOLE}} Configuration)
Line 32: Line 32:
 
and the subelements:
 
and the subelements:
  
* Description;
+
* Description
* [[InputServices]];
+
* [[#InputServices|InputServices]]
* [[OutputServices]];
+
* [[#OutputServices|OutputServices]]
* [[DequeueFilter]].
+
* [[Op-type#DequeueFilter|DequeueFilter]]
 +
 
 +
===InputServices===
 +
 
 +
Before doing any communication you can run an ordered list of input services.
 +
 
 +
This section allows the definition of input services for the current communication operation. The current version of {{GVESB}} provides the following services:
 +
* Data Transformation
 +
* XML Validation
 +
* OGNL Scripting
 +
 
 +
The InputServices Element is used by: [[GVIteratorOperationNode]] and '''GVOperationNode'''.
 +
 
 +
Might contain the following elements:
 +
* Description
 +
* [[gvdte-service]]
 +
* [[xml-validation-service]]
 +
* [[ognl-script-service]]
 +
 
 +
===OutputServices===
 +
 
 +
After doing any communication you can run an ordered list of output services.
 +
 
 +
This section allows the definition of output services for the current communication operation.  The current version of {{GVESB}} provides the following services:
 +
* Data Transformation
 +
* XML Validation
 +
* OGNL Scripting
 +
 
 +
The OutputServices Element is used by [[ChangeGVBufferNode]], [[GVIteratorOperationNode]] and '''GVOperationNode'''.
 +
 
 +
Might contain the following elements:
 +
* Description
 +
* [[gvdte-service]]
 +
* [[xml-validation-service]]
 +
* [[ognl-script-service]]
 +
 
 +
====gvdte-service====
 +
 
 +
Invokes the Data Transformation Engine (GVDTE). Refer to the documentation GVDTE for information on features of {{GVESB}} Data Transformation Engine.
 +
 
 +
The following table shows the gvdte-service element's attributes:
 +
{|class="gvtable"
 +
! Attribute !! Type !! Description
 +
|-
 +
| type || fixed || This attribute must assume the value '''service'''.
 +
|-
 +
| internal || fixed || This attribute must assume the value '''yes'''.
 +
|-
 +
| critical || optional || Defines if the service is critical. A critical service failure mark the entire communication as failed.
 +
The attribute's default value is: yes.
 +
|-
 +
| remove-fields || optional || Indicates whether or not to remove from the buffer the fields used for communication with GVDTE.
 +
The attribute's default value is: yes.
 +
|}
 +
 
 +
Its subelements are:
 +
* Description
 +
* [[map-name-param]]
 +
* [[gvdte-context-call]]
 +
* [[gvdte-extra-param]]

Revision as of 11:36, 22 February 2012

Description

A GVOperationNode is an operation node indicating that GreenVulcano® ESB must perform a communication with an external systems (invocation, sending messages, receiving messages). For example, if the node indicates a receive a message (see attribute op-type), you can also define a DequeueFilter that sets certain conditions that the received message must meet.

VulCon / GV Console Configuration

The GVOperationNode is a Flow element. It has the following attributes:

  • type: flow-node;
  • class: it.greenvulcano.gvesb.core.flow.GVOperationNode.
  • id: ID of the node. Unique within the 'Flow' and its value cannot be null.
  • op-type: The attribute admitted values are:
    • call
    • enqueue
    • dequeue
  • input: Specifies the input (from the execution environment) for the operation.
    If the input is an exception, the operation is not performed, and the output is set equal input exception. Its value can't be null.
  • output: The operation's output (GVBuffer or Exception) is inserted into the execution environment with this exact name.
    Default to "input" value. The attribute value can't be null.
  • next-node-id: Indicates the next node in the workflow to execute when the operation ends.
  • id-system: Identifies the system involved in communication. Can be selected from systems declared as Participant in the Operation section.
    The attribute value can't be null.
  • operation-name: Identifies the communication operation selected by the channel of the system indicated by the id-system attribute.
    Only the operations of the type declared in the 'op-type' attribute can be selected. Its value cannot be null.
  • point-x: X position of the node in the VulCon® workflows editor. Immutable, used by VulCon®.
  • point-y: Y position of the node in the VulCon® workflows editor. Immutable, used by VulCon®.
  • dump-in-out: If true enable the dump of the input/output GVBuffer. Default false. The attribute admitted values are:
    • true
    • false
  • dump-env-in-out: If true enable the dump of the input/output Execution Environment. Default false. The attribute admitted values are:
    • true
    • false


and the subelements:

InputServices

Before doing any communication you can run an ordered list of input services.

This section allows the definition of input services for the current communication operation. The current version of GreenVulcano® ESB provides the following services:

  • Data Transformation
  • XML Validation
  • OGNL Scripting

The InputServices Element is used by: GVIteratorOperationNode and GVOperationNode.

Might contain the following elements:

OutputServices

After doing any communication you can run an ordered list of output services.

This section allows the definition of output services for the current communication operation. The current version of GreenVulcano® ESB provides the following services:

  • Data Transformation
  • XML Validation
  • OGNL Scripting

The OutputServices Element is used by ChangeGVBufferNode, GVIteratorOperationNode and GVOperationNode.

Might contain the following elements:

gvdte-service

Invokes the Data Transformation Engine (GVDTE). Refer to the documentation GVDTE for information on features of GreenVulcano® ESB Data Transformation Engine.

The following table shows the gvdte-service element's attributes:

Attribute Type Description
type fixed This attribute must assume the value service.
internal fixed This attribute must assume the value yes.
critical optional Defines if the service is critical. A critical service failure mark the entire communication as failed.

The attribute's default value is: yes.

remove-fields optional Indicates whether or not to remove from the buffer the fields used for communication with GVDTE.

The attribute's default value is: yes.

Its subelements are: