Loading...
Recommendations
Explore
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”.
Use the Debugger
Mirth® Connect by NextGen Healthcare User Guide
Debugger Window
The following context-specific tasks are available: Number Name Description 1 Title And Menu Bar The Title identifies the Chanel ID and the Event Name or Connector Identifier for the selected channel. The Menu Bar allows you to perform actions on the Debugger window. 2 Coding Area The Coding area displays Mirth® Connect code and custom JavaScript associated with the channel debugger 3 Local Variables Area The Local Variables area shows the values and values and the current state of local variables associated with the debugger results. 4 Expressions Area The Expressions area allows you to evaluate an expression to determine what a value is. You can also evaluate a snippet of code in this area. 5 Thread Information Bar The Thread Information bar identifies the following information: Connector type (Ex: JavaScript Writer) Channel Name (Ex: “Debugger Channel”) Channel ID Location of JavaScript (Ex: destination “Physician (2)” where “Physician” is the name of a destination connector and “2”
Mirth® Connect by NextGen Healthcare User Guide
Mirth® Connect Debugger
The Mirth Connect Debugger tool allows you to troubleshoot JavaScript errors throughout the Mirth® Connect application. The Debugger can be used for the following scripts and connectors: Deploy, Undeploy, Preprocessor, and Post Processor scripts Attachment/Batch scripts Source Connectors: Filters/Transformers Database Reader and JavaScript Reader types Destination Connectors: Filters/Transformers. Database Writer and JavaScript Writer types Response transformers Before You Begin If your Java application does not interact directly with a user, use the following steps to change the Headless mode to false. Setting this mode to false means that your Java application: Displays windows or dialog boxes. Accepts keyboard or mouse input. Uses any heavyweight AWT (Abstract Windowing Toolkit) components. To Edit the mcserver.vmoptions file Use the Debugger Debugger Window Debugger Menus Parent topic: Mirth Connect and JavaScript
Mirth® Connect by NextGen Healthcare User Guide
Use Deploy/Start Dependencies if one channel depends on another to operate correctly.
This can be configured in the Channel Summary view > Set Dependencies > Deploy/Start Dependencies. By defining channel dependencies, you can protect yourself against deploying a channel without deploying another channel that it depends on to operate correctly. Mirth® Connect will alert you when you attempt to deploy a channel that depends on another: Parent topic: Channel Configuration
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
Mirth® Connect by NextGen Healthcare User Guide
Debug Channel
The Debug Channel dialog allows you to deploy the currently selected channel while debugging specific scripts within the channel. Select any number of scripts you would like to debug, and then select OK to deploy the channel and begin debugging. Parent topic: Channel Tasks
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