Debugger Window

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” is the destination number)

Mirth® Connect by NextGen Healthcare User Guide

Debugger Menus

File Menu Edit Menu Debug Menu Window Menu Coding Area Parent topic: Mirth Connect Debugger

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

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

Coding Area

Number Name Description 1 Title The Title identifies the Chanel ID and the Event Name or Connector Identifier for the selected channel. 2 Internal Code This is the thread interruption point which appears where the internal code of the debug option starts (i.e., the “importClass – function() ”. line). As you test your script, you can see the state of various objects and variables in the lines prior to the interruption line. 3 Custom JavaScript Any custom JavaScript displays normally within the “doScript() ” boundary. Parent topic: Debugger Menus

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

Variable Maps

Throughout the Message Processing Lifecycle, your channels and messages have access to various maps. Depending on the scope, the map may only be available in the current channel/connector, or may be globally available across your entire system. These variable maps allow you to store a piece of information that can be used later (in a downstream channel, connector, or somewhere else). A common use for these variables is to provide easy drag-and-drop for connector properties. The Destination Mappings list will display all available connector/channel map variables for example. They are also used in other ways, such as populating Custom Metadata Columns. The following variable maps exist throughout Mirth® Connect: Name JavaScript Variable Get/Put Shortcut Variable Response Map responseMap $r Connector Map connectorMap $co Channel Map channelMap $c Source Map sourceMap $s Global Channel Map globalChannelMap $gc Global Map globalMap $g Configuration Map configurationMap $cfg The table above

Debugger Window

Recommendations

Debugger Menus

Use the Debugger

Mirth® Connect Debugger

Coding Area

Channel Properties

Variable Maps

Debugger Menus

Use the Debugger

Mirth® Connect Debugger

Coding Area

Channel Properties

Variable Maps