Anonymous: /* BpelFlow */

2012-11-12T10:27:28Z

‎BpelFlow

Anonymous: /* {{GVESB}} configuration */

2012-04-10T13:10:52Z

‎{{GVESB}} configuration

Anonymous: Created page with "==Description== Defines an operational workflow of {{GVESB}}. Each workflow is identified by a couple and is made instantiating a Flow, with Bpe..."

2012-04-10T13:10:13Z

Created page with "==Description== Defines an operational workflow of {{GVESB}}. Each workflow is identified by a couple <service,operation> and is made instantiating a Flow, with Bpe..."

New page

==Description==

Defines an operational workflow of {{GVESB}}.

Each workflow is identified by a couple <[[service]],[[operation]]> and is made instantiating a [[Flow]], with Bpel operations.

The operations you can configure are:
* 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}}.

Using the sub-element 'Conditions' can be (re)defined the conditions for possible use in the workflow routing.

=={{GVESB}} configuration==

The BpelOperation Element is used by: [[Service]].

The following table shows its attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| type || fixed || Unmodifiable. Used by {{GVESB}} factory framework.
This attribute must assume the value '''operation'''.
|-
| name || required || BpelOperation's name. Corresponds to a {{GVESB}} 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
The attribute's value cannot be null.
|-
| forward-name || optional || Forward's name.
Must be specified only if you are setting up a workflow for a forward.
Must not be specified for the {{GVESB}} communication primitive.
The attribute's value cannot be null.
|-
| out-check-type || required || Enable a consistency check of [[GVBuffer]].
The attribute's admitted values are:
* none: does not make any check.
* sys-svc: fields 'system' and 'service' the result should take the same values as 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'.
|-
| operation-activation || optional || Activation status of the current service operation.
The attribute's admitted values are:
* on: the operation is active.
* off: the operation is not active.
The attribute's default value is: on.
|}

Might contain the sub-element:
* [[Description]]
* [[BpelFlow]]

===BpelFlow===

The BpelFlow Element is used by: [[BpelOperation]].

The following table shows its attributes:
{|class="gvtable"
! Attribute !! Type !! Description
|-
| namespace || required ||
|-
| processname || required ||
|}

Might contain the sub-element:
* [[Description]]

← Older revision		Revision as of 10:27, 12 November 2012
Line 65:		Line 65:

	===BpelFlow===		===BpelFlow===
		+	This element defines a GreenVulcanoESB Bpel workflow.

	The BpelFlow Element is used by: [[BpelOperation]].		The BpelFlow Element is used by: [[BpelOperation]].

@@ Line 62: / Line 62: @@
 Might contain the sub-element:
 * [[Description]]
-* [[BpelFlow]]
+* [[#BpelFlow|BpelFlow]]
 ===BpelFlow===

BpelOperation - Revision history

Anonymous: /* BpelFlow */

Anonymous: /* {{GVESB}} configuration */

Anonymous: Created page with "==Description== Defines an operational workflow of {{GVESB}}. Each workflow is identified by a couple and is made instantiating a Flow, with Bpe..."