Difference between revisions of "Dh-call"
(→VulCon / GV Console Configuration) |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Definition== | ==Definition== | ||
| − | A | + | |
| + | A [[dh-call]] is the operation that must be configured into {{L_VULCON}} or {{L_GVCONSOLE}} [[System|System section]], to define the parameters for making a call to the [[DataHandler]]. | ||
| + | |||
| + | The DBOBuilder to be invoked is defined by: | ||
| + | * the input GVBuffer DH_SERVICE_NAME property value | ||
| + | * the input GVBuffer.service field value | ||
==VulCon / GV Console Configuration== | ==VulCon / GV Console Configuration== | ||
| − | In order to add a | + | In order to add a [[dh-call]] operation you must define the following fields: |
{|class="gvtable" | {|class="gvtable" | ||
| Line 13: | Line 18: | ||
| class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation | | class || fixed || This attribute must assume the value '''it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation | ||
|- | |- | ||
| − | | name || required || | + | | name || required || This field identifies the operation name that you will use in service definition. |
|} | |} | ||
| − | The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a | + | The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a [[dh-call]] operation: |
<syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?> | <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?> | ||
| Line 33: | Line 38: | ||
| − | To use a | + | To use a [[dh-call]] in a {{GVESB}} service, you need to define a node of type [[GVOperationNode]] into your [[Service]] element and define in the field ''operation-name'' the name defined in the [[dh-call]] operation. |
| − | The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a | + | The following example shows the configuration generated from {{L_VULCON}} or {{L_GVCONSOLE}} when you configure a [[dh-call]] operation in {{GVESB}} service: |
<syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?> | <syntaxhighlight lang="XML"><?xml version="1.0" encoding="UTF-8"?> | ||
| Line 50: | Line 55: | ||
<Participant id-channel="CHANNEL-NAME" id-system="SYSTEM-NAME"/> | <Participant id-channel="CHANNEL-NAME" id-system="SYSTEM-NAME"/> | ||
<Flow first-node="excel_reader" point-x="20" point-y="112"> | <Flow first-node="excel_reader" point-x="20" point-y="112"> | ||
| − | <GVOperationNode class="it.greenvulcano.gvesb.core.flow.GVOperationNode" | + | <GVOperationNode |
| − | + | class="it.greenvulcano.gvesb.core.flow.GVOperationNode" | |
| − | + | dump-in-out="false" id="process" | |
| − | + | id-system="GVESB" input="input" | |
| − | + | next-node-id="end" op-type="call" | |
| − | + | operation-name="TestInsertXML" output="output" | |
| + | point-x="127" point-y="139" type="flow-node"/> | ||
<GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode" | <GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode" | ||
| − | + | end-business-process="yes" id="end" op-type="end" | |
| − | + | output="excel_xml" point-x="358" point-y="112" | |
| − | + | type="flow-node"/> | |
</Flow> | </Flow> | ||
</Operation> | </Operation> | ||
| Line 69: | Line 75: | ||
| − | At this point you have configured a service with a | + | At this point you have configured a service with a [[dh-call]] operation. |
| − | Into the | + | Into the [[dh-call]] it is possible to insert three elements: |
| − | * Description | + | * [[Description]] |
| − | * [[Retriever Config]] | + | * [[Retriever Config]] |
| − | * [[DBOBuilder]] | + | * [[DBOBuilder]] |
Latest revision as of 08:51, 20 November 2012
Definition
A dh-call is the operation that must be configured into VulCon® or GV Console® System section, to define the parameters for making a call to the DataHandler.
The DBOBuilder to be invoked is defined by:
- the input GVBuffer DH_SERVICE_NAME property value
- the input GVBuffer.service field value
VulCon / GV Console Configuration
In order to add a dh-call operation you must define the following fields:
| Attribute | Type | Description |
|---|---|---|
| type | fixed | This attribute must assume the value call. |
| class | fixed | This attribute must assume the value it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation |
| name | required | This field identifies the operation name that you will use in service definition. |
The following example shows the configuration generated from VulCon® or GV Console® when you configure a dh-call operation:
<?xml version="1.0" encoding="UTF-8"?>
<GVSystems name="SYSTEMS" type="module">
<Systems>
<System id-system="system-name" system-activation="on">
<Channel id-channel="CHANNEL_NAME">
<dh-call class="it.greenvulcano.gvesb.virtual.datahandler.DataHandlerCallOperation"
name="TestInsertXML" type="call"/>
</Channel>
</System>
</Systems>
</GVSystems>
To use a dh-call in a GreenVulcano® ESB service, you need to define a node of type GVOperationNode into your Service element and define in the field operation-name the name defined in the dh-call operation.
The following example shows the configuration generated from VulCon® or GV Console® when you configure a dh-call operation in GreenVulcano® ESB service:
<?xml version="1.0" encoding="UTF-8"?>
<GVServices name="SERVICES" type="module">
<Groups>
<Group group-activation="on" id-group="DEFAULT_GRP"/>
</Groups>
<Services>
<Service group-name="DEFAULT_GRP" id-service="SERVICE-NAME"
service-activation="on">
<Client id-system="SYSTEM-NAME" statistics="off" system-activation="on">
<Operation name="RequestReply" operation-activation="on"
out-check-type="none" type="operation">
<Participant id-channel="CHANNEL-NAME" id-system="SYSTEM-NAME"/>
<Flow first-node="excel_reader" point-x="20" point-y="112">
<GVOperationNode
class="it.greenvulcano.gvesb.core.flow.GVOperationNode"
dump-in-out="false" id="process"
id-system="GVESB" input="input"
next-node-id="end" op-type="call"
operation-name="TestInsertXML" output="output"
point-x="127" point-y="139" type="flow-node"/>
<GVEndNode class="it.greenvulcano.gvesb.core.flow.GVEndNode"
end-business-process="yes" id="end" op-type="end"
output="excel_xml" point-x="358" point-y="112"
type="flow-node"/>
</Flow>
</Operation>
</Client>
</Service>
</Services>
</GVServices>
At this point you have configured a service with a dh-call operation.
Into the dh-call it is possible to insert three elements:
