Logging with JavaScript

Mirth® Connect by NextGen Healthcare User Guide

Message Variables

There are a wide variety of different JavaScript contexts throughout Mirth® Connect, and each have various variables automatically available from the local scope. Here are some common examples: message: A string that represents a raw inbound message in native format. msg: An XML object that represents a transformed version of the inbound message. tmp: An XML object that represents an outbound message template; available only if an outbound template is defined. connectorMessage: An instance of the ImmutableConnectorMessage Java class; an internal representation of the message and its attributes. Parent topic: Using JavaScript in Mirth Connect

Mirth® Connect by NextGen Healthcare User Guide

Using JavaScript in Mirth® Connect

This section shows you how to use JavaScript to perform various messaging operations within Mirth® Connect. About E4X Accessing Message Data with E4X Adding Segments to a Message Segments are a group of fields that can contain varying types of data. Each segment exists independently and can be used in multiple messages. Deleting a Segment Iterating Over Message Segments Iterating Over Repeating Fields Adding a New Repeating Field Message Variables Built-In Code Templates Using Java Classes Regular Expressions Logging with JavaScript Generating a Hash with JavaScript How to generate a hash using Javascript. Parent topic: Mirth Connect and JavaScript

Mirth® Connect by NextGen Healthcare User Guide

Server Tab

The Server tab enables you to enter details about your ports, server memory, log levels, and view log files. The following fields are available on the Server page. Function Description Web Start Port Accesses the launch page for the Mirth® Connect Administrator. Default: 8080 Administrator Port This port is used by the Mirth Connect Administrator to communicate with the Mirth® Connect Server. Default: 8443 Server Memory (mb) The server's maximum available memory (Java max heap size). By default this is 256 MB, but for large production instances you will typically want to increase this value. Main Log Level Database Log Level Channel Log Level These fields enables you to select the applicable log level from the drop-down menus. Available options include: ERROR WARN INFO DEBUG TRACE Depending on the log level, messages of the selected level or lower will pass into that level's log when the system logs a certain-level message. Refresh Select this button to update the most recent list of l

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

Opening the Java Client Console

If an error occurs on the Mirth® Connect server, you will typically see one or more entries appear in the Logs. If an error occurs in the Mirth Connect Administrator, it is possible that it is isolated to the client-side only, and so nothing will appear in the server-side logs. In cases like this, it is useful to enable the Java Client Console to see any exceptions that occur on your client-side Java virtual machine (JVM). To enable the console, first open the Java Control Panel: In your System Preferences (on OSX) or the Control Panel (on Windows), open the Java section. A new dialog will appear: Select on the Advanced tab. Select Show console. Select Apply, then select OK. Now when you launch the Administrator, you will see a second window also pop-up: Any exceptions that are logged to stdout / stderr on the client side will appear in that console. Parent topic: Troubleshooting

Mirth® Connect by NextGen Healthcare User Guide

4.6.1 Upgrade Notes

This topic covers the improvements and new features included in Mirth® Connect version 4.6.1. Updating Minimum Supported Java Version in Mirth® ConnectWith the release of 4.6.1, Mirth® Connect Java 17 is the minimum supported Java version. Changes to Logging Configuration The log4j2.properties file has a new property named property.logs that sets a relative or an absolute path to the desired log file directory. This replaces the dir.logs property that is now deprecated. For this property to work properly, the values for appender.rolling.fileName and appender.rolling.filePattern need to begin with ${logs}/. When you upgrade to version 4.6.1 by using the installer wizard, the log directory selected in the Select Data Paths step is saved as property.logs in the log4j2.properties file. If you upgrade by using a different method, property.logs is automatically added with the same value as dir.logs when the server restarts for the first time. If you have not changed the appender.rolling.file

Logging with JavaScript

Recommendations

Message Variables

Using JavaScript in Mirth® Connect

Server Tab

Mirth® Connect Debugger

Opening the Java Client Console

4.6.1 Upgrade Notes

Logging with JavaScript

Message Variables

Using JavaScript in Mirth® Connect

Server Tab

Mirth® Connect Debugger

Opening the Java Client Console

4.6.1 Upgrade Notes