About Command Center Processor Role

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Polling and Pruning Roles

One requirement of the Advanced Clustering plugin is that all participating servers in the cluster be connected to a single, shared database. Because of this requirement, the plugin needs to enforce that only one server in the cluster is assigned to execute the data pruner on its defined schedule. Likewise, a similar problem exists for channels with polling source connectors (File Reader, Database Reader, JavaScript Reader). Typically, a polling source connector polls a shared file system or an external database, in which case, not all servers in the cluster should perform this operation. If they did, you may end up with the same HL7 message file being processed once for each server in the cluster. To avoid this problem, the Advanced Clustering plugin designates one server in the cluster to perform these polling operations. To designate a particular server as the preferred "polling" or "pruning" server, select the appropriate server by selecting its radio button in the Node Configurati

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

About Cluster Settings

The Clustering page includes clustering configuration settings that you can modify. This table contains the configuration settings that appear on the Clustering page, including a description of each element. Setting Name Description Default Value Possible Values Heartbeat Interval The frequency (in milliseconds) to send heartbeats and channel status updates to the cluster. 1000 200-9999 Heartbeat Timeout If a node fails to send a heartbeat within the set number of milliseconds, it is considered disconnected from the cluster. 300000 100-9999 Cluster Sync Interval The frequency (in milliseconds) to query the cluster for new tasks to execute. These tasks handle membership changes, message recovery, role changes, and server name changes. 1000 100-9999 Dashboard Status Sync Interval The frequency (in milliseconds) to query the cluster to update channel dashboard statuses. 1000 100-9999 Cluster Log Sync Interval The frequency (in milliseconds) to query the cluster to update alert logs, conne

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 Advanced Clustering Configuration

When the Advanced Clustering plugin is installed, the Clustering tab appears on the Settings page in Mirth® Connect. Image of the Clustering tab on the Settings page On this page, you can configure various timing settings used by the Advanced Clustering plugin. The page also features - in the Node Configuration section - a list of servers that have registered with the cluster, including status information about each server. Image of the Node Configuration section on the Clustering tab About Cluster Settings The Clustering page includes clustering configuration settings that you can modify. About Polling and Pruning Roles About Command Center Processor Role This topics helps you understand how to use the Advanced Clustering feature in conjunction with the Command Center Base plug-in. About IP Address and Ports

Mirth® Connect by NextGen Healthcare Command Center User Guide

Command Center Tasks

With the Command Center, you can perform certain tasks as mentioned below. The Mirth® Connect by NextGen Healthcare Command Center contains some tasks that you can perform and some that the system performs. You can register and unregister your Mirth® Connect by NextGen Healthcare environment and configure the clustering settings. The system automatically starts a sync task to sync your Mirth® Connect by NextGen Healthcare environment. The Command Center tasks are as follows: Register Task You can register a Mirth Connect server or cluster with Mirth Command Center. This action does the following: Starts any of the standard polling, message reporting, and any other core or feature extension-related tasks Adds all Mirth Connect database values that define its registration with the Mirth Command Center When you register a Mirth Connect cluster, the cluster gets a single environmentId shared among all the Mirth Connect servers in the cluster. You can automatically register a Mirth Connect

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Strict Mode Enabled

This option is enabled by default to preserve the behavior of the clustering plugin upon upgrade to 3.12 or later. When this option is enabled, the Advanced Clustering extension ensures that all channel operations (deploy/undeploy/start/stop/etc.) are fully synchronized across the entire cluster, meaning that only one deploy/start/etc operation can be running at any given time. In addition, new servers that start up and attempt to join this cluster will be blocked by the following operations: Other servers starting up / joining the cluster Performing a channel deploy/undeploy/start/stop/pause/resume Performing a connector start/stop task Performing the Remove All Messages task for a channel Performing the Remove Results task for a channel Deleting a channel Performing message recovery for an offline server The clustering plugin does this by having each server obtain two locks as part of the startup process: startupDeploy: This lock prevents other servers from entering the startup proce

About Command Center Processor Role

Recommendations

About Polling and Pruning Roles

About Cluster Settings

About IP Address and Ports

About Advanced Clustering Configuration

Command Center Tasks

Strict Mode Enabled

About Command Center Processor Role

About Polling and Pruning Roles

About Cluster Settings

About IP Address and Ports

About Advanced Clustering Configuration

Command Center Tasks

Strict Mode Enabled