Download the Advanced Clustering Plug-in

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Install and Set Up Without Mirth® Appliance by NextGen Healthcare

This section instructs you how to install and set up advanced clustering without Mirth® Appliance by NextGen Healthcare. Before you begin Verify that each Mirth® Connect server in the cluster is running the same version of Mirth® Connect and has the same set of plugins installed. This section instructs you how to install and set up advanced clustering without Mirth® Appliance by NextGen Healthcare. Prepare a highly available database to be used as the cluster's shared database. Supported databases for clustering are the same as Mirth® Connect itself: PostgreSQL 8.3+ MySQL 5.0+ Oracle 10gR2+ SQL Server 2005+ Modify the database connection settings on each server to point to your highly available database. Image of the Database Settings tab where you configure database connection settings. Open the Mirth® Connect Administrator on each server, and install the Advanced Clustering plugin zip file (that you downloaded from the Success Community under the Extensions section. To view clusterin

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Run the Mirth® Connect Clustering Setup Wizard

(On the primary appliance) In the navigation bar, click Applications, and select Mirth Connect > Manage > Clustering > Wizard. Image of the Wizard option on the Applications menu. Follow the steps in the wizard. Note: You only need to run the wizard on one server in the cluster, and it will configure all servers as needed. The wizard will prompt you to upload the Advanced Clustering plugin zip file. Use the file you downloaded from Success Community. After you perform all steps in the wizard, your cluster setup is complete. Parent topic: Download the Advanced Clustering Plug-in

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Advanced Configuration

Configuring Max Cluster Log Queue Sizes By default, the cluster log queues have a maximum size of 10,000 messages. If you see logs not being recorded or warnings about the queues being close to full or full and you have spare resources, you can increase or decrease the queues using the .vmoptions files (mcserver.vmoptions or mcservice.vmoptions). You can set the max queue size for the alert log with: -Dmirth.clustering.alertlog.maxqueue= 20000 You can set the max queue size for the connection log with: -Dmirth.clustering.connectionlog.maxqueue= 20000 You can set the max queue size for the server log with: -Dmirth.clustering.serverlog.maxqueue= 20000 Parent topic: Download the Advanced Clustering Plug-in

Mirth® Appliance by NextGen Healthcare Deployment Guide, 4.1

Mirth® Connect Advanced Clustering

Mirth® Connect has the ability to run in a clustered environment to provide high availability and improved performance. Mirth® Connect is likely installed on your appliance, which means there is a Mirth® Connect entry in the Applications menu that provides access to the configuration windows for Mirth® Connect clustering. Mirth® Connect can run in a clustered environment to provide high availability and improved performance when you are using the Advanced Clustering plugin, which is available to Platinum subscribers. You can set up two appliances, previously set up with database replication and automatic failover, and the Mirth® Connect Clustering plugin, to provide a highly-available network endpoint for message processing backed by a single, highly-available database. Mirth Appliance by NextGen Healthcare Features Mirth® Appliance by NextGen Healthcare supports a number of clustering features when you are using the Advanced Clustering plugin. Parent topic: Applications Menu

Mirth® Connect by NextGen Healthcare User Guide

Advanced Clustering

The Advanced Clustering plug-in improves the availability of your Mirth® Connect cluster with automatic message takeover. If one server in the cluster fails, another server will automatically resume processing of any queued or unfinished messages from the failed server. Managing your cluster becomes easier as you can monitor the status of each server, deploy/start/stop/pause channels across all servers, and view message statistics for the whole cluster or a particular server from the Mirth® Connect dashboard. This plug-in can be used with standalone Mirth® Connect instances using your own load-balancing solution, but also seamlessly integrates with the load-balancing and failover services provided on Mirth Appliances. Contact Us if you have any questions. Image of the Advanced Clustering extension features Parent topic: Services and Extensions

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

Download the Advanced Clustering Plug-in

Recommendations

Install and Set Up Without Mirth® Appliance by NextGen Healthcare

Run the Mirth® Connect Clustering Setup Wizard

Advanced Configuration

Mirth® Connect Advanced Clustering

Advanced Clustering

About Advanced Clustering Configuration

Install and Set Up Without Mirth® Appliance by NextGen Healthcare

Run the Mirth® Connect Clustering Setup Wizard

Advanced Configuration

Mirth® Connect Advanced Clustering

Advanced Clustering

About Advanced Clustering Configuration