Use Deploy/Start Dependencies if one channel depends on another to operate correctly.

Mirth® Connect by NextGen Healthcare User Guide

Deploy/Start Channels

When you start a channel, the Mirth® Connect Administrator automatically checks if there are any dependencies of the channel that should be started first. If there are, they will be shown in a special dialog: By default only the channels you have selected will be bolded in the dialog, meaning that only they will be started. If you want to start the other channels in the dependency chain as well, check the " Start/resume # additional channels " check box before selecting the OK button. Upon pressing OK the channels will be deployed in the numeric order shown in the dialog. The numbered list in this dialog indicates the different "tiers" in the dependency graph. Any downstream dependencies will be deployed / started first, and only then will their dependent channels be deployed / started. In the example picture above, if the checkbox is checked, the channel labeled 1. will be started first, then the channel labeled 2., and then finally the channel labeled 3., which was the original chann

Mirth® Connect by NextGen Healthcare User Guide

Channel Configuration

Use tags to categorize your channels Place any reusable JavaScript code into Code Template functions and organize them into Code Template Libraries. Use Custom Meta Data Columns to increase the performance of searching the message history on a particular message field. Use Deploy/Start Dependencies if one channel depends on another to operate correctly. Use multiple resource folders for your Java libraries if you need to limit library usage to specific channels or if you have many Java libraries. Use tags to categorize your channels Place any reusable JavaScript code into Code Template functions and organize them into Code Template Libraries. Use Custom Meta Data Columns to increase the performance of searching the message history on a particular message field. Use Deploy/Start Dependencies if one channel depends on another to operate correctly. Use multiple resource folders for your Java libraries if you need to limit library usage to specific channels or if you have many Java librari

Mirth® Connect by NextGen Healthcare User Guide

Deploy/Start Dependencies

Channel Dependencies allow you to mark one channel as a "dependency" of another channel. This means that the dependency channel should be started / deployed before the dependent channel. This could be for a variety of reasons, but one common use-case is when you have one channel sending to another channel. The upstream channel is the dependent, and the downstream would be the dependency. The tree in the top-half of the dialog shows dependencies of the current channel. In other words, channels that show up in the top tree are those that the current channel depends upon. By expanding nodes in this tree, you can see descendant dependencies, or "dependencies of the dependencies". The tree in the bottom-half of the dialog shows channels that are dependent on the current channel. By expanding nodes in this tree, you can see descendant dependents, or"channels that are dependent on the channel that is dependent on the current channel". Select the Add / Remove buttons next to either tree to add

Mirth® Connect by NextGen Healthcare User Guide

Use the Debugger

Note: mcservice.exe is currently not supported for Debug mode. Debug mode is not recommended for Clustering environment (Basic or Advanced Clustering). Within Mirth® Connect, select Channels. In the Channels list, select the channel you would like to debug. Note: You can currently only debug one channel at a time. In Channel Tasks, select Debug Channel. On the Debug Channel window, select the channel script(s) you would like to use to debug the selected channel. Select OK. A separate debugger window opens for each selected script, and for each destination connector. Process the selected channel (For Example: send a message). The Debugger window(s) will pop-up based on the options you selected. To exit the debug mode, close the debugger window(s) or undeploy the channel. Note: The channel will not stop or undeploy properly if the debugger is waiting for user operation, such as selecting “Go”. Parent topic: Mirth Connect Debugger

Mirth® Connect by NextGen Healthcare User Guide

Pause/Stop/Undeploy Channels

This follows similarly from deploying/starting channels, except that the logic is reversed. When pausing/stopping/undeploying a channel, the operation is performed on dependent channels (channels that are dependent on the selected channel) first. As in the deploy/start case, by default only the channels you have selected will be bolded in the dialog, meaning that only they will be paused/stopped/undeployed. If you want to perform this action on the other channels in the dependency chain as well, check the "additional channels" check box before selecting the OK button. Upon selecting OK the channels will be paused/stopped/undeployed in the numeric order shown in the dialog. Parent topic: Deploy/Start Dependencies

Mirth® Connect by NextGen Healthcare User Guide

Channel Properties

Item Name Description A Name The name of the channel. Only alphanumeric (a-z / 0-9) characters, spaces, hyphens, and underscores are allowed. B Enabled Indicates whether the channel is ready to be deployed. All enabled channels will automatically be deployed with the Mirth® Connect by NextGen Healthcare server starts up. If there is an error in your channel configuration, this will automatically be unchecked. C Set Data Types Dialog Configure data types across your entire channel, from the source connector to each of your destination connectors. Allows easy bulk editing of data type properties. For additional information, see Set Data Types. D Clear global channel map on deploy If checked, the global channel map for this channel will be cleared out whenever the channel is redeployed. E Set Dependencies Configures Code Template Libraries, Library Resources, and Deploy/Start Dependencies for this channel. For more information, see Set Dependencies Window. F Initial State Determines what

Use Deploy/Start Dependencies if one channel depends on another to operate correctly.

Recommendations

Deploy/Start Channels

Channel Configuration

Deploy/Start Dependencies

Use the Debugger

Pause/Stop/Undeploy Channels

Channel Properties

Deploy/Start Channels

Channel Configuration

Deploy/Start Dependencies

Use the Debugger

Pause/Stop/Undeploy Channels

Channel Properties