Difference between revisions of "Channel"
(→Description) |
|||
| Line 9: | Line 9: | ||
=={{VULCON}} / {{GVCONSOLE}} Configuration== | =={{VULCON}} / {{GVCONSOLE}} Configuration== | ||
| − | The | + | The Channel is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{{GVESB}}} offers a wide variety of Operations: |
| − | |||
| − | |||
| − | |||
| − | |||
'''File management''': | '''File management''': | ||
Revision as of 11:24, 27 February 2013
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 is identified by an unique attribute id-channel, this attribute is unique within the System entity.The Channel subelement are the Operations, {{{GVESB}}} offers a wide variety of Operations:
File management:
WebService
Query DB
JMS queue
Routes
j2ee-calls
mm7-calls
util-calls
comm-calls
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.
