GVSystems

Description

Each GreenVulcano^® ESB operation that requires an interface to an external application is defined within a channel. A channel is a grouping of operations. The operations can be grouped into a channel according to you prefer rule: usually operations are grouped by technology or external application to which interfaced, but the division of operation within the channel is completely arbitrary. A system is a group of channels.

GVSystem configuration

File:GVSystemStrucure.gif

GVSystem structure

The following picture shows the structure of GVSystems element.

<GVSystems name="SYSTEMS" type="module">
        <Systems>
            <Description>This section contains a list of all systems connected to GreenVulcano ESB</Description>
            <System id-system="GVESB_WS" system-activation="on">
                <Channel id-channel="TEST_CHANNEL_A">
                    <test-service-call class="it.greenvulcano.gvesb.virtual.internal.TestServiceCall"
                                       name="toupper_call" service="toupper" type="call"/>
                    <test-service-call class="it.greenvulcano.gvesb.virtual.internal.TestServiceCall"
                                       name="tolower_call" service="tolower" type="call"/>
                    <jms-enqueue acknowledge-type="auto-acknowledge"
                                 class="it.greenvulcano.gvesb.virtual.j2ee.JMSEnqueueOperation"
                                 connection-factory="java:/XAConnectionFactory"
                                 delivery-mode="persistent"
                                 destination-name="gvesb/jms/queue/TOUPPER_A_Request_Queue"
                                 destination-type="queue" dump-message="true"
                                 name="JMSEnqueueTo::TOUPPER_A_Req" priority="4"
                                 ref-dp="WriteString_JMSBytesMessageDataProvider"
                                 transacted="false" type="enqueue">
                        <XAHelper auto-enlist="false" transaction-status="TMSUCCESS"/>
                    </jms-enqueue>
                    <jms-dequeue acknowledge-type="auto-acknowledge"
                                 class="it.greenvulcano.gvesb.virtual.j2ee.JMSDequeueOperation"
                                 connection-factory="java:/XAConnectionFactory"
                                 destination-name="gvesb/jms/queue/TOUPPER_A_Response_Queue"
                                 destination-type="queue" dump-message="true"
                                 name="JMSDequeueFrom::TOUPPER_A_Resp"
                                 receive-timeout="10000"
                                 receive-timeout-overridable="false"
                                 receive-type="timeout"
                                 ref-dp="ReadString_JMSBytesMessageDataProvider"
                                 transacted="false" type="dequeue">
                        <XAHelper auto-enlist="false" transaction-status="TMSUCCESS"/>
                    </jms-dequeue>
                </Channel>
                <Channel id-channel="TEST_CHANNEL_FILE">
                </Channel>   
            </System>

GVSystems element contains only one Systems element. The Systems element contains one or more System elements, each System element contains one or more Channels. In each channel you can define the Operations.

The GVSystems Element is used by: GVCore. The following table shows its attributes:

Attribute	Type	Description
type	fixed	This attribute must assume the value module.
name	fixed	This attribute must assume the value SYSTEMS.

GVSystems contains the following sub-element:

• Description
• Systems

Systems

This section defines the configuration of systems connected to GreenVulcano^® ESB and shows the technologies used for interfaces, the connection parameters, etcetera.

Contains the sub-element:

• Description
• System