Difference between revisions of "GVCoreCallNode"

From GreenVulcano Wiki
Jump to: navigation, search
(→‎{{GVESB}} Configuration)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
=={{GVESB}} Configuration==
+
=={{VULCON}} / {{GVCONSOLE}} Configuration==
  
−
GVCoreCallNode element allows direct invocation of a {{GVESB}} core workflow.
+
GVCoreCallNode element allows direct invocation of a {{GVESB}} core workflow, is a [[Flow]] element that extends [[FlowNode]].
  
 
Dynamic fields can contains [[placeholders]].
 
Dynamic fields can contains [[placeholders]].
Line 8: Line 8:
 
{|class="gvtable"
 
{|class="gvtable"
 
! Attribute !! Tyte !! Description
 
! Attribute !! Tyte !! Description
−
|-
 
−
| type || fixed || This attribute must assume the value '''flow-node'''.
 
 
|-
 
|-
 
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVCoreCallNode'''.
 
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.core.flow.GVCoreCallNode'''.
 
|-
 
|-
 
| op-type || fixed || This attribute must assume the value '''corecall'''.
 
| op-type || fixed || This attribute must assume the value '''corecall'''.
−
|-
 
−
| id || required || ID of the node. Unique within the [[Flow]].
 
 
|-
 
|-
 
| dynamic || optional || If 'true'  id-system, id-service and operation attributes can contains [[placeholders|metadata]] to be resolved at runtime.
 
| dynamic || optional || If 'true'  id-system, id-service and operation attributes can contains [[placeholders|metadata]] to be resolved at runtime.
Line 21: Line 17:
 
| id-service || required || Name of service to invoke.
 
| id-service || required || Name of service to invoke.
 
|-
 
|-
−
| id-system || required || Name of service's client.
+
| id-system || optional || Name of service's client.
 
|-
 
|-
 
| operation || required || Name of service's operation to invoke
 
| operation || required || Name of service's operation to invoke
Line 29: Line 25:
 
|-
 
|-
 
| change-log-context || optional || If 'true' log context is updated.
 
| change-log-context || optional || If 'true' log context is updated.
−
The default is 'false'.
+
The default is 'true'.
 
|-
 
|-
−
| input || required || Specifies the input (from the execution environment) for the operation.
+
| input-ref-dp || optional || Name of [[Data_provider|Data Provider]] to use for input manipulation.
−
If the input is an exception, the operation is not performed, and the output is set equal input exception.
+
This Data Provider will receive in input a [[GVBuffer]] and must return the object to be inserted in GVBuffer.object.
 
|-
 
|-
−
| output || optional || The operation's output ([[GVBuffer]] or Exception) is inserted into the execution environment with this exact name.
+
| output-ref-dp || optional || Name of [[Data_provider|Data Provider]] to use for output manipulation.
−
Default to "input" value.
+
This Data Provider will receive in input a [[GVBuffer]] and must return the object to be inserted in GVBuffer.object.
 +
|}
 +
 
 +
<div class="version_ge3.4.0.9">
 +
{|class="gvtable"
 +
! Attribute !! Tyte !! Description
 
|-
 
|-
−
| next-node-id || required || Indicates the next node in the workflow to execute when the operation ends.
+
| change-log-master-service || optional || If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file.
−
|-
+
Used only if @change-log-context is true.
−
| point-x || optional || X position of the node in the VulCon workflows editor.
 
−
Immutable, used by {{L_VULCON}}.
 
−
|-
 
−
| point-y || optional || Y position of the node in the VulCon workflows editor.
 
−
Immutable, used by {{L_VULCON}}.
 
−
|-
 
−
| dump-in-out || optional || If true enable the dump of the input/output [[GVBuffer]].
 
−
Default false.
 
−
|-
 
−
| dump-env-in-out || optional || If true enable the dump of the input/output Execution Environment.
 
 
Default false.
 
Default false.
 
|}
 
|}
 +
</div>
 +
 +
and the subelements:
 +
<div class="version_ge3.4">
 +
* [[GVOperationNode#InputServices|InputServices]]
 +
* [[GVOperationNode#OutputServices|OutputServices]]
 +
</div>

Latest revision as of 20:03, 28 October 2015

VulCon / GV Console Configuration

GVCoreCallNode element allows direct invocation of a GreenVulcano® ESB core workflow, is a Flow element that extends FlowNode.

Dynamic fields can contains placeholders.

The following table shows the GVCoreCallNode element's attributes:

Attribute Tyte Description
class fixed This attribute must assume the value it.greenvulcano.gvesb.core.flow.GVCoreCallNode.
op-type fixed This attribute must assume the value corecall.
dynamic optional If 'true' id-system, id-service and operation attributes can contains metadata to be resolved at runtime.
id-service required Name of service to invoke.
id-system optional Name of service's client.
operation required Name of service's operation to invoke
overwrite-sys-svc optional If 'true' SYSTEM and SERVICE fields of GVBuffer will be overwritten.

The default is 'false'.

change-log-context optional If 'true' log context is updated.

The default is 'true'.

input-ref-dp optional Name of Data Provider to use for input manipulation.

This Data Provider will receive in input a GVBuffer and must return the object to be inserted in GVBuffer.object.

output-ref-dp optional Name of Data Provider to use for output manipulation.

This Data Provider will receive in input a GVBuffer and must return the object to be inserted in GVBuffer.object.

Attribute Tyte Description
change-log-master-service optional If true change the log master service with the used one (configured or calculated), in order to write log messages into a different log file.

Used only if @change-log-context is true. Default false.

and the subelements:

Retrieved from "https://gvwiki.greenvulcano.com/gvwiki/index.php?title=GVCoreCallNode&oldid=4446"