About Guaranteed Message Order

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About IP Address and Ports

When using the Advanced Clustering plugin, nodes send notifications to each other to improve performance. This is especially important if using the Guarantee Message Order option on any channels. To enable nodes to receive notifications, you must specify the IP address of each node, as well as the port that each node should listen for notifications on. The IP address is automatically populated with a "best guess," but you may need to manually change it if the value is not correct. The port is set to "10000" by default, but you can change it to any other port number. Note: The port must be available on the node to receive notifications and benefit from improved performance. To disable receiving notifications on a node, set its port to a blank value. This will lead to decreased performance. Parent topic: About Advanced Clustering Configuration

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Configuring the Source Connector

If Guarantee Message Order is enabled in the Source Connector of a channel, only one message will be processed at any time across the entire cluster for that particular channel. Additionally, if the source queue is enabled, it will be processed only on one node in the cluster. Parent topic: About Guaranteed Message Order

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 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

Mirth® Connect by NextGen Healthcare User Guide

Channel Performance

Adjust the Message Storage slider so that the channel only retains the message data that you will actually need. If large messages are expected, use an Attachment Handler to improve throughput and reduce memory and disk usage. Enable source queuing if an auto-generated acknowledgement is sufficient for the upstream system. Enable destination queuing if you do not need to respond to the originating system from your destination. 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 Increase the Queue Threads value if the downstream system can accept multiple concurrent connections. Clear the "Wait for previous destination" checkbox, unless you need destinations to process messages one after another. Use the "Destination Set Filter" feature in your source transformer when you need to route messages to only one (or a subset) of destinations in your channel. Adjust the Message Storage slider so that the cha

Mirth® Connect by NextGen Healthcare User Guide

Advanced Queue Settings

Item Name Description A Retry Count Before Queue/Error The maximum number of times the connector attempts to send the message before queuing or erroring. B Retry Interval (ms) The amount of time (in milliseconds) that should elapse between retry attempts to send messages. This interval applies to both the queue and initial retry attempts. C Rotate Queue If enabled, when any message fails to be sent from the queue, the connector will place the message at the end of the queue and attempt to send the next message. This will prevent a single message from holding up the entire queue. If the order of messages processed is important, this should be disabled. D Regenerate Template Regenerate the template and other connector properties by replacing variables each time the connector attempts to send the message from the queue. If this is disabled, the original variable replacement is used for each attempt. E Include Filter/Transformer If enabled, the filter and transformer is re-executed before

About Guaranteed Message Order

Recommendations

About IP Address and Ports

About Configuring the Source Connector

About Configuring a Destination Connector

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

Channel Performance

Advanced Queue Settings

About IP Address and Ports

About Configuring the Source Connector

About Configuring a Destination Connector

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

Channel Performance

Advanced Queue Settings