Difference between revisions of "Channel"
(→Description) |
(→Description) |
||
| Line 1: | Line 1: | ||
==Description== | ==Description== | ||
| + | |||
| + | The '''Operations''' are grouped into '''Channels''', how organize the '''Operation''' within the '''Channels''' is a choice of {{GVESB}} 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. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
A '''Channel''' brings together a set of operations to a [[System]]. Generally, the operations contained in a channel are related to each other: for example, operations such as enqueue / dequeue that work on the same queue will be contained in the same channel. | A '''Channel''' brings together a set of operations to a [[System]]. Generally, the operations contained in a channel are related to each other: for example, operations such as enqueue / dequeue that work on the same queue will be contained in the same channel. | ||
Revision as of 10:53, 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.
A Channel brings together a set of operations to a System. Generally, the operations contained in a channel are related to each other: for example, operations such as enqueue / dequeue that work on the same queue will be contained in the same channel.
In general for any system there will be a single channel that collects all the operations necessary for communication to the system. But there may be situations where it is preferable to use multiple channels.
Typical examples where you can use multiple channels are:
- Technology: Some servers may have different technological interfaces (eg HTTP, RMI), then you can allocate more channels to group operations according to the technology used.
- Abstraction: It is possible that a system is actually composed by multiple heterogeneous systems (such situation can occur, for example, during a migration, or due to modification or replacement of systems).
For each subsystem, you can 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:
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.
