Op-type

Description

This attribute indicates the type of operation that must execute.

The available operations are:

• call: if you want GreenVulcano^® ESB to perform an invocation.
• enqueue: if you want GreenVulcano^® ESB to perform a send a message.
• dequeue: if you want GreenVulcano^® ESB to execute a receipt of a message.
  In this case you can also enter a sub-element DequeueFilter.
• corecall: if you want GreenVulcano^® ESB to execute an internal service call.
• check
• notification
• save
• wait
• change GVBuffer
• end.

DequeueFilter

Used in GVOperationNode with op-type set to dequeue, allows you to define the criteria for receiving messages.
Will be received only messages that meet the criteria.

This element has not attributes.

May have one or more subelements of the following types:

• IDFilter: would set the criteria of the received message ID.
• RetCodeFilter: would set the criteria on the return code of the received message.
• SystemFilter: would set the criteria field system of the received message.
• ServiceFilter: would set the criteria in the field service of the received message.
• PropertyFilter: would set the criteria on the properties of the received message

If multiple policies are specified, then the message to receive must meet them all.

IDFilter

Allows to receive only messages with the ID equal to that specified in the request.

You can specify only one active instance of IDFilter.

Its attributes are:

Attribute	Type	Description
type	fixed	This attribute must assume the value filter
name	fixed	This attribute must assume the value IDFilter
use-input	fixed	Always uses the input GVBuffer.id. Unmodifiable. This attribute must assume the value yes
enabled	required	Specifies whether the filter is active or not. Can be used to disable the filter temporarily without deleting it from the configuration. The admitted values are: yes no

Might contain the subelement Description.

RetCodeFilter

Lets you specify a condition on the return code field the received message must meet.

Through attributes 'min' and 'max' you can specify a range of allowable values for the return code.

You can specify only one active instance of RetCodeFilter.

Its attributes are:

Attribute	Type	Description
type	fixed	This attribute must assume the value filter
name	fixed	This attribute must assume the value RetCodeFilter
use-input	fixed	Always uses the input GVBuffer.id. Unmodifiable. This attribute must assume the value no. If no, the 'min' and/or 'max' attributes must be defined
enabled	required	Specifies whether the filter is active or not. Can be used to disable the filter temporarily without deleting it from the configuration. The admitted values are: yes no
min	optional	Specifies the minimum acceptable value for the return code field.
max	optional	Specifies the maximum acceptable value for the return code field.

Might contain the subelement Description.

SystemFilter

Lets you specify a condition on the system field the received message must meet.

Can constrain the system field to a fixed constant, or require that the system field is the same as the request.

You can specify only one active instance of SystemFilter.

Its attributes are:

Attribute	Type	Description
type	fixed	This attribute must assume the value filter
name	fixed	This attribute must assume the value SystemFilter
use-input	fixed	Always uses the input GVBuffer.id. Unmodifiable. This attribute must assume the value no. If 'yes' then requires that the field system of the received message has the same value of the field system of the request. If 'no' then requires that the field system of the received message has the value specified by 'value'. In this case, the 'value' attribute must be defined
enabled	required	Specifies whether the filter is active or not. Can be used to disable the filter temporarily without deleting it from the configuration. The admitted values are: yes no
value	optional	System field value of the received message. Meaningful only if 'use-input' is set to 'no'.

Might contain the subelement Description.

ServiceFilter

Lets you specify a condition on the service field the received message must meet.

Can constrain the service field to a fixed constant, or require that the service field is the same as the request.

You can specify only one active instance of ServiceFilter.

Its attributes are:

Attribute	Type	Description
type	fixed	This attribute must assume the value filter
name	fixed	This attribute must assume the value ServiceFilter
use-input	fixed	Always uses the input GVBuffer.id. Unmodifiable. This attribute must assume the value no. If 'yes' then requires that the field service of the received message has the same value of the field service of the request. If 'no' then requires that the field service of the received message has the value specified by 'value'. In this case, the 'value' attribute must be defined
enabled	required	Specifies whether the filter is active or not. Can be used to disable the filter temporarily without deleting it from the configuration. The admitted values are: yes no
value	optional	Service field value of the received message. Meaningful only if 'use-input' is set to 'no'.

Might contain the subelement Description.

PropertyFilter

Lets you specify a condition on a property the received message must meet.

Can constrain the property to a fixed constant, or require that the property is the same as the request.

You can specify multiple instances of PropertyFilter to work on different fields.

Its attributes are:

Attribute	Type	Description
type	fixed	This attribute must assume the value filter
name	fixed	This attribute must assume the value PropertyFilter
use-input	fixed	Always uses the input GVBuffer.id. Unmodifiable. This attribute must assume the value no. If 'yes' then requires that the field service of the received message has the same value of the field service of the request. If 'no' then requires that the field service of the received message has the value specified by 'value'. In this case, the 'value' attribute must be defined
enabled	required	Specifies whether the filter is active or not. Can be used to disable the filter temporarily without deleting it from the configuration. The admitted values are: yes no
property	required	Name of property to which to apply the filter. The name of the property used on the filter will be prefixed with the string 'p$'.
value	optional	Property value of the received message. Meaningful only if 'use-input' is set to 'no'.

Might contain the subelement Description.