Channel Tasks

Channel Name

The name to assign to this channel. Each channel must have a unique name, may not have more than 40 characters, and must not contain any special characters.

Incoming Data

Selects the format of data the channel should expect to come in.

Initial State

Selects whether the channel should start as soon as it is deployed (or when Mirth is started), or should wait to be manually started.

Enabled

Check this box to enable the channel. Channels that are not enabled (disabled) are not deployed, and are inactive as a result.

Use Transactional Endpoints

Checking transactional endpoints causes all database destination connectors to join a single atomic transaction. If any database command fails on any destination, every other database command will be rolled back. This option has no effect on database connectors using JavaScript.

Strip Namespace From Messages

Check this box to automatically remove XML namespace declarations from incoming messages. This option is useful for mapping data received over a web service that includes multiple namespaces.

Synchronize channel

Synchronizing a channel enforces the following rules:

• All destinations will be executed in the order they are defined in the destination list.
• The source connector will wait for all destinations to complete before sending a response (if any).
• Each destination's response is available for inspection in the Postprocessor.
• The Postprocessor is executed after every destination has completed processing.

A synchronized channel will operate utilizing a single execution thread per message received. Message order is not guaranteed if a channel is not synchronized. Synchronization is required to send response data from a destination back to a source connector. LLP queuing is not recommended on a synchronized channel.

Revision

Displays the current revision of the channel. The revision starts at zero when the channel is first created and is automatically incremented each time the channel is modified and saved.

Last Modified

Displays the date and time when the channel was last changed and saved.

Encrypt messages in database

Check this box to have the channel's messages stored in an encrypted form for privacy, or leave it unchecked to store the messages in clear form for maximum performance.

Store message data

Check this box to store messages for the channel, or uncheck it to not store messages. A channel configured to not store its messages can handle more messages per second than the channel configured to store its messages. It is best to store messages "With errors only" when running in a production environment.

Do not store filtered messages

Check this box to not store messages which are rejected by the channel's connector filters, or leave it unchecked to store these messages.

With errors only

Check this box to store only messages that had an error while processing, or leave it unchecked to store all messages.

Store indefinitely

Check this radio button to disable the pruning of messages for this channel.

Prune messages after

Check this radio button to discard stored messages after the entered number of days. See also Message Pruner section for a more flexible message pruning approach.

Description

Enter the free-form text description of this channel here.