Difference between revisions of "Channel"
(Created page with "==Description== A '''Channel''' brings together a set of interfaces to a System. Generally, the interfaces contained in a channel are related to each other: for example, ope...") |
(→{{VULCON}} / {{GVCONSOLE}} Configuration) |
||
| Line 21: | Line 21: | ||
Its possible subelements are: | Its possible subelements are: | ||
| − | ''' | + | '''File management''': |
| − | * ''filereader-call'' | + | * ''[[filereader-call]]'' |
| − | * ''filewriter-call'' | + | * ''[[filewriter-call]]'' |
| − | * ''filemanager-call'' | + | * ''[[filemanager-call]]'' |
| − | * ''fsmonitor-call'' | + | * ''[[fsmonitor-call]]'' |
| − | * ''remotemanager-call'' | + | * ''[[remotemanager-call]]'' |
| − | * '' shell-call''. | + | * ''[[shell-call]]''. |
| − | ''' | + | '''WebService''' |
| − | * ''ws-call'' | + | * ''[[ws-call]]'' |
| − | ''' | + | '''Query DB |
| − | * ''db-call'' | + | * ''[[db-call]]'' |
| − | * ''dh-call'' | + | * ''[[dh-call]]'' |
| − | * ''birt-report-call'' | + | * ''[[birt-report-call]]'' |
| − | * ''excel-call'' | + | * ''[[excel-call]]'' |
'''JMS queue''' | '''JMS queue''' | ||
| − | * ''jms-enqueue'' | + | * ''[[jms-enqueue]]'' |
| − | * ''jms-dequeue'' | + | * ''[[jms-dequeue]]'' |
'''Routes''' | '''Routes''' | ||
| − | * ''routed-dequeue'' | + | * ''[[routed-dequeue]]'' |
| − | * ''routed-enqueue'' | + | * ''[[routed-enqueue]]'' |
| − | ''' | + | '''Mail''' |
| − | * ''smtp-call'' | + | * ''[[smtp-call]]'' |
| − | * ''pop-call'' | + | * ''[[pop-call]]'' |
'''j2ee-calls''' | '''j2ee-calls''' | ||
| − | * ''j2ee-ejb-call'' | + | * ''[[j2ee-ejb-call]]'' |
| − | * ''j2ee-jca-call | + | * ''[[j2ee-jca-call]]'' |
| − | |||
'''mm7-calls''' | '''mm7-calls''' | ||
| − | * ''mm7-decode-call'' | + | * ''[[mm7-decode-call]]'' |
| − | * ''mm7-submit-call'' | + | * ''[[mm7-submit-call]]'' |
'''util-calls''' | '''util-calls''' | ||
| − | * ''extract-data-call'' | + | * ''[[jmx-call]]'' |
| − | * ''routed-call'' | + | * ''[[extract-data-call]]'' |
| − | * ''test-service-call'' | + | * ''[[routed-call]]'' |
| − | * ''excelreader-call'' | + | * ''[[test-service-call]]'' |
| − | * ''generic-call'' | + | * ''[[excelreader-call]]'' |
| + | * ''[[generic-call]]'' | ||
'''comm-calls''' | '''comm-calls''' | ||
| − | * ''http-call'' | + | * ''[[http-call]]'' |
| − | * ''hl7-call'' | + | * ''[[hl7-call]]'' |
| − | * ''jbpm-call'' | + | * ''[[jbpm-call]]'' |
| − | * ''jbpm-task-call'' | + | * ''[[jbpm-task-call]]'' |
| − | * ''openspcoop-call'' | + | * ''[[openspcoop-call]]'' |
==How To== | ==How To== | ||
From the {{L_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. | From the {{L_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. | ||
Revision as of 11:46, 30 January 2012
Description
A Channel brings together a set of interfaces to a System. Generally, the interfaces 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.
