4.1.3. Channel detail
All the information required to configure a channel is displayed here, split into different tabs. Tabs are presented in a logical order starting with the gateway for the incoming message, going to message transformation, gateway for the outgoing message, email notifications, routing rules, and finally testing.
This tab displays the following information. You can change it by just editing the fields and click on Save.
|
The name of the channel. |
|
|
The description of the channel. |
|
|
A channel can be disabled to be ignored by future deployments. A disabled channel is just as a deleted channel, except that you can keep it for future use. An enabled channel is just a 'normal' channel, and all its changes will be reflected to the production system at every deployment. |
|
|
Tells what will happen with this channel at next deployment. 'Apply Changes' means that the channel is already in production but has changed since the last deployment; the changes will be deployed. 'Start' means the channel is not yet in production, but will be after next deployment. 'Stop' means the channel is currently in production, but will be removed at next deployment. 'No change' means nothing will be done about this channel at next deployment. |
|
|
How long the message processed by this channel will be kept. This value can also be set at environment level. |
It also displays information about date and times where the channel was created or last updated.
The Delete action allows you to delete your channel.
The Duplicate action allows you to duplicate your channel.
The top right corner shows important information: the status of the channel (Inactive or Active).
You will find more information in the deployment section.
Note: You can change the storage duration to the most suitable time for you from (15 days, 1 month, 3 months, 1 year, 2 years, 10 year) in each channel individually of for all of your environment so each channel will have different storage duration than each other.
Select the channel and from "General" select the requested "Storage duration", as shown below.
Storage duration
After that don't forget to deploy your environment in order to push this changes to production.
When you increase the storage duration other than the default then there will be a additional charges.
The gateway In specifies the way incoming messages are communicated from the sources external system to Babelway. Babelway supports a large variety of protocols, including FTP, AS2, HTTP, Email, OFTP, SFTP, X400 or web upload.
You can find all information about how to define and configure gateways in the gateways chapter.
The message In precisely describes the structure of the incoming message.
You can find all information about how to define and configure message definitions in the message definitions chapter.
The transformation tells Babelway how the incoming message should be translated to the outgoing message.
You can find all information about how to define and configure transformations, including the behavior of the visual drag-and-drop editor, in the transformations chapter.
The message Out precisely describes the structure of the outgoing message.
You can find all information about how to define and configure message definitions in the message definitions chapter.
The gateway Out specifies how the outgoing message should be communicated to the target external system.
You can find all information about how to define and configure gateways in the gateways chapter.
For each individual channel, you may configure automatic notifications that send emails to specified addresses upon arrival of new messages. Notified users can be different if the message has been successfully processed or if an error has been generated.
You can find all information about how to define and configure notifications in the notifications chapter.
The routing allows you to define which channel must process a message, when multiple channels use the same gateway In.
You can find all information about how to define and configure gateways in the routing chapter.
The test cases are a great way to be sure that your channels are correctly configured, and produce the expected results.
You can find all information about how to define and configure gateways in the test cases chapter.
The following tabs give you quick links to many other elements of the application that are related to this channel :
|
Channel used as base for this channel. |
|
|
Channels based on this channel. |
|
|
Displays the channels using the current channel's gateway In. |
|
|
Displays the channels using the current channel's message In. |
|
|
Displays the channels using the current channel's message Out. |
|
|
Displays the channels using the current channel's gateway Out. |
|
|
Channel from which the current channel receives messages. |
|
|
Channels following the current channel to execute advance functions. |
|
|
Redirect you to the messages list containing only the messages of this channel. |