Library Resources

Library Context	Description
Channel	This is the root-level node of the tree, and includes all contexts below it. If one of the resource check boxes in the table below is in the indeterminate state (grey box), it means that it is currently included on some but not all of the sub-contexts.
Channel Scripts	This includes the deploy, undeploy, preprocessor, postprocessor, attachment, and batch scripts.
Source Connector	This includes the source filter / transformer script, as well as the source connector itself. For example if you are using a Database Reader and you include a resource containing a custom JDBC Driver JAR, that will be available for use on the connector.
Destination Connectors	This includes the filter / transformer scripts, the response transformer scripts, and the destination connector itself. For example if you are using a JavaScript Writer and you include a resource containing custom Java classes, those will be available for use inside the destination script.

Mirth® Connect by NextGen Healthcare User Guide

Connector-Specific Properties

Every connector has its own custom set of properties. The properties you configure for a TCP Listener will be different from a Database Writer and so on. Here is a list of source and destination connectors supported by Mirth® Connect: Source Connectors Channel Reader DICOM Listener Database Reader File Reader HTTP Listener JMS Listener JavaScript Reader TCP Listener Web Service Listener Destination Connectors Channel Writer DICOM Sender Database Writer Document Writer File Writer HTTP Sender JMS Sender JavaScript Writer SMTP Sender TCP Sender Web Service Sender Additional connectors are made available as extensions: Email Reader Serial Connector NextGen Results CDR Connector FHIR Connector Interoperability Connector Suite Parent topic: Connector Components

Mirth® Connect by NextGen Healthcare User Guide

Code Template Contexts

Similar to how a code template library can be included only on specific channels, code templates can further be isolated to specific scripts. This can be helpful for ensuring that there are no conflicts between function names, and also for better memory usage, since not all code templates need to be compiled in with all scripts across your entire server. The script contexts are organized into groups, allowing you to easily include a code template in, for example, all global scripts, in a single select. The following groups are displayed: Global Scripts: The global deploy/undeploy/preprocessor/postprocessor scripts, not specific to any particular channel. For additional information, see Edit Global Scripts View. Channel Scripts: The channel-level deploy/undeploy/preprocessor/postprocessor scripts (more info here) , as well as the JavaScript Attachment Handler and JavaScript Batch Adapter (for additional information, see Data Types) . Source Connector: The source filter/transformer scrip

Mirth® Connect by NextGen Healthcare User Guide

JMS Sender

This destination connector connects to an external JMS provider and writes messages to a queue or topic. It supports both JNDI and specifying a specific connection factory. Once this connector dispatches a message, the connection to the JMS provider will be kept open and cached until the connector is stopped or an error occurs. The properties view also includes a mechanism to save configuration templates for common provider types, so that creating a new JMS Sender is as quick and easy as possible. Note: Depending on the JMS connection provider you are using, you may need to include some external libraries (JARs) as a Library Resource and include them using the Set Dependencies dialog on the Channel Summary tab. For example, to use connection templates included for ActiveMQ and JBoss, you should download the libraries from their official site in order to use them with the JMS connectors. Supported property groups: Destination Settings Item Name Default Value Description A Use JNDI No Se

Mirth® Connect by NextGen Healthcare User Guide

JMS Listener

This source connector connects to an external JMS provider and reads messages from a queue or topic. It supports both JNDI and specifying a specific connection factory, as well as fine-tuned queries through a configurable selector. Once this connector is started, it will attempt to keep a persistent open connection to the JMS provider. If for any reason the connection is dropped, the connector will automatically reconnect without any intervention needed. The properties view also includes a mechanism to save configuration templates for common provider types, so that creating a new JMS Listener is as quick and easy as possible. Note: Depending on the JMS connection provider you are using, you may need to include some external libraries (JARs) as a Library Resource and include them using the Set Dependencies dialog on the Channel Summary tab. For example, to use connection templates included for ActiveMQ and JBoss, you should download the libraries from their official site in order to use

Mirth® Connect by NextGen Healthcare User Guide

Other Files and Folders

The various files and folders present in the installation directory are used to contain application configuration files and other executables. Other files and folders present in the Installation Directory include the following: cli-lib: Libraries used by the Command Line Interface. These should not be changed. client-lib: Libraries used by the Mirth Connect Administrator. These should not be changed. custom-lib: Custom libraries can be dropped in this folder, to be used by the default library resource. docs: Contains license information for Mirth® Connect and all third-party libraries. Also contains the Javadoc documentation used by User API. extensions: Extension libraries used by the Server, Administrator, and CLI. These should not be changed. logs: This is the default location that server logs will be written into. This can be changed from the log4j2.properties file. manager-lib: Libraries used by the Server Manager. These should not be changed. mccommand(.exe): The entrypoint scrip

Mirth® Connect by NextGen Healthcare User Guide

Resources Settings Tab

The Resource Settings tab lets you configure shared objects or libraries that can be used across the entire server or on specific channels and connectors. Resources are shared services that can be used in specific channels and connectors or in other places throughout the Mirth® Connect server. They may include custom Java libraries to use within scripts or services to handle outbound connections. Image of the Resource Settings tab. Resources Table Columns Tasks Reload Resource Directory Resource Using Resources in Channels/Connectors Parent topic: Settings View

Library Resources

Recommendations

Connector-Specific Properties

Code Template Contexts

JMS Sender

JMS Listener

Other Files and Folders

Resources Settings Tab

Connector-Specific Properties

Code Template Contexts

JMS Sender

JMS Listener

Other Files and Folders

Resources Settings Tab