Channel

Description

The Operations are grouped into Channels, how organize the Operation within the Channels is a choice of GreenVulcano^® ESB developer

Usually the Operations are grouped by:

• Technology: Some servers may have different technological interfaces (eg HTTP, RMI), then you can allocate additional channels to group operations based on the technology used.
• Abstraction: It 'possible that a system is actually composed of several heterogeneous systems (such a situation can occur, for example, during a migration, or due to modification or replacement of systems). For each subsystem is possible to build a Channel.

VulCon / GV Console Configuration

The Channel Element is used by System. It has the attribute:

• id-channel: ID of the channel. This identifier must be unique within the System and cannot be null.

Its possible subelements are:

File management:

• filereader-call
• filewriter-call
• filemanager-call
• fsmonitor-call
• remotemanager-call
• shell-call.

WebService

• ws-call

Query DB

• db-call
• dh-call
• birt-report-call
• excel-call

JMS queue

• jms-enqueue
• jms-dequeue

Routes

• routed-dequeue
• routed-enqueue

Mail

• smtp-call
• pop-call

j2ee-calls

• j2ee-ejb-call
• j2ee-jca-call

mm7-calls

• mm7-decode-call
• mm7-submit-call

util-calls

• jmx-call
• extract-data-call
• routed-call
• test-service-call
• excelreader-call
• generic-call

comm-calls

• http-call
• hl7-call
• jbpm-call
• jbpm-task-call
• openspcoop-call

How To

From the VulCon^® Core view, it is possible to insert a new Channel by right clicking the System element you are working on. Then Insert after and press Channel*. A new Channel element will be created. Fill the id-channel property in the properties view. Now you can insert all the operations needed.