About Configuring the Source Connector

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Configuring a Destination Connector

In any Destination Connector, if Queue Messages is set to "On Failure" or "Always", then the Use Single Cluster Node setting is available in the Advanced Queue Settings. Select from the following options: Yes: The destination queue is processed by a single node. Use this option, in conjunction with Guarantee Message Order in the Source Connector, to preserve message order across the entire cluster. No: The destination queue is processed concurrently by all nodes in the cluster. Message order is not guaranteed. Use Source Setting: The destination queue is processed by a single node only if Guarantee Message Order is enabled in the Source Connector. Parent topic: About Guaranteed Message Order

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Guaranteed Message Order

Guaranteed message ordering is used to ensure that messages received by a channel are processed in the order that they are received. This reduces the throughput of the channel, so it is important to configure the IP address and port for each node in the cluster in order to mitigate the decrease in performance. (For details about IP address/port, see About IP Address and Ports.) About Configuring the Source Connector About Configuring a Destination Connector

Mirth® Connect by NextGen Healthcare User Guide

Source Connector

Every channel has exactly one source connector which gets data into Mirth® Connect from an external system. The source connector is configured on the Source Tab within the Edit Channel View. In addition to the standard Connector Components, source connectors include: A Source Queue that can be enabled or disabled. When enabled, the channel acts as a store-and-forward service that can receive messages and send acknowledgements immediately to the originating system, without having to wait for the message to process through the entire channel. A Batch Processor that can be enabled or disabled. When enabled, the channel takes any incoming data and splits it into multiple messages that each proceed discretely through the channel. See Batch Processing for additional information. A Response Selector that determines what response to send back to the originating system, if applicable. You can choose to auto-generate a response based on the inbound data type of the source transformer. You can al

Mirth® Connect by NextGen Healthcare User Guide

Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system.

If you do not need to send back a response to the originating system, or the response does not need to come from one of your destinations, consider turning the "Source Queue" ON in your source connector. This lets the channel respond to the originating system immediately on message receipt, rather than waiting for the message to finish processing. This can increase your channel's overall throughput. Parent topic: Channel Performance

Mirth® Connect by NextGen Healthcare User Guide

Reprocess Message

When you select the Reprocess Message task, a confirmation dialog pops up. You are given the option to overwrite the existing message or process the data through the channel as a completely new message. You can also choose to exclude certain destinations from being executed during the reprocess operation. Note that the message will always flow through the Source Connector first, regardless of which destinations you exclude. When a message is reprocessed, two new Source Map variables are injected into the message: reprocessed: Boolean indicating that the current message is the result of a reprocess operation. When present, the value of this variable is always true. replaced: Boolean indicating that the current message was overwritten as a result of a reprocess operation. Parent topic: Message Browser Tasks

Mirth® Connect by NextGen Healthcare User Guide

Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time

This setting controls how many messages the channel can process simultaneously (on separate CPU threads). The default value is 1, which means that only one message can be processed by the channel at a time and also guarantees that messages are sent out from the channel in the order that they are received. Increasing this value eliminates the order guarantee, but can greatly increase throughput when a large number of messages is received in a short amount of time. Setting this value too high however, can harm throughput. Keep in mind that this setting controls how many CPU threads are used by the channel. So, it is important to consider how many threads the CPU can execute concurrently as well as how much of the CPU's resources are needed by other channels/processes. Parent topic: Channel Performance

About Configuring the Source Connector

Recommendations

About Configuring a Destination Connector

About Guaranteed Message Order

Source Connector

Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system.

Reprocess Message

Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time

About Configuring a Destination Connector

About Guaranteed Message Order

Source Connector

Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system.

Reprocess Message

Increase the Max Processing Threads value if message order is not important and you may receive a large number of messages in a short time