JMS Listener

Item	Name	Default Value	Description
A	Use JNDI	No	Select Yes to use JNDI to look up a connection factory to connect to the queue or topic. Select No to specify a connection factory class without using JNDI.
B	Provider URL		If using JNDI, enter the URL of the JNDI provider here.
C	Initial Context Factory		If using JNDI, enter the fully-qualified Java class name of the JNDI Initial Context Factory class here.
D	Connection Factory Name		If using JNDI, enter the JNDI name of the connection factory here.
E	Connection Factory Class		If using the generic JMS provider and not using JNDI, enter the fully-qualified Java class name of the JMS connection factory here.
F	Connection Properties		This table allows you to enter custom connection factory settings. The Property column is the key, while the Value column is the actual value for the setting. The specific properties used here will vary depending on what connection factory class / provider you are using.
G	Username		The username for accessing the queue or topic.
H	Password		The password for accessing the queue or topic.
I	Destination Type	Queue	Specify whether the destination is a queue or topic. When connecting to a topic, you can check the Durable checkbox so that all messages published to the topic will be read, regardless of whether or not a connection to the broker is active. If unchecked, only messages published while a connection is active will be read.
J	Destination Name		The name of the queue or topic.
K	Client ID		The JMS client ID to use when connecting to the JMS broker.
L	Reconnect Interval (ms)	10000	The number of milliseconds between reconnect attempts in the case that a connection error occurs.
M	Selector		Enter a selector expression to select specific messages from the queue/topic. Leave blank to read all messages.
N	Connection Templates		This section allows you to save the current state of your JMS Listener properties into a template, which may then be restored later if you make changes, or may also be applied to other JMS Listener connectors. For additional information, see JMS Connection Templates.

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

Web Service Listener

This source connector publishes a SOAP endpoint via JAX-WS. By default it uses a simple service with one operation that takes in a message string and sends back a response string. The SOAP XML envelope is automatically handled, so that the actual data the channel receives is the content within the operation argument node. You also have the option to provide your own custom service, with custom operations. Supported property groups: Listener Settings Source Settings HTTP Authentication Settings Item Name Default Value Description A Web Service Default service If Custom is selected, provide the fully-qualified class name of the Endpoint service you wish to publish. B Service Class Name com.mirth.connect.connectors.ws.DefaultAcceptMessage The fully-qualified class name of the Endpoint service to publish. C Service Name Mirth The name of the service, used to populate the URL context path. D Binding Default The selected binding version defines the structure of the generated envelope. Select

Mirth® Connect by NextGen Healthcare User Guide

HTTP Listener

This source connector acts as an HTTP server, listening for requests from one or more remote clients. The messages sent to the channel can be the raw payload, or an XML document allowing multipart payloads to be parsed in a consistent and easy-to-use way. The HTTP payload can be either Base64 encoded or converted using a charset, depending on the Content-Type. Responses that go back to each client can be fully configured, including custom response headers. Finally, static resources or directories can be automatically hosted, to allow the connector to act as a simple web server that serves specific content. Additional options are available with the SSL Manager extension. Supported property groups: Listener Settings Source Settings HTTP Authentication Settings Item Name Default Value Description A Base Context Path The context path for the HTTP Listener URL. Note: If this is specified, any requests made at this base context path must have a trailing slash in the request URI. B Receive Ti

Mirth® Connect by NextGen Healthcare User Guide

Library Resources

Resources are shared services that can be used in specific channels / 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. The Library Resources tab allows you to include resources throughout your entire channel, or in more specific contexts such as the channel scripts or certain connectors. The Library Context tree in the top section of the tab allows you to select a specific context, or the Channel root-level node which represents all contexts across your channel at once. The following library contexts are available: 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,

Mirth® Connect by NextGen Healthcare User Guide

Batch Processing

Batch Processing allows a channel to receive a single message, but split it into multiple messages that each get processed through the channel. When using this along with a source connector that supports streaming (File Reader, TCP Listener in MLLP mode), batch processing has the added benefit of not having to read the entire file into memory all at once, but instead only one message at a time. For example with the File Reader and batch processing you can read in files that are gigabytes in size, without causing any memory issues for your Mirth Connect server. Data types that support batch processing will have a Batch Properties section in the source inbound data type properties. To enable batch processing, set Process Batch to Yes in the Source Settings. To change how an incoming message is split into multiple messages, look at the Batch Properties section of the source inbound data type you are using. For example, the Delimited Text Data Type has options to split by record delimiter,

Mirth® Connect by NextGen Healthcare User Guide

General Channel Properties

General Channel properties are configured on the Summary Tab within the Edit Channel View and include: Unique ID, name, and description. Links to Code Template Libraries: These let the channel know which custom functions are available in specific JavaScript contexts. Links to Library Resources: These let the channel know which custom Java classes are available in specific connectors and/or JavaScript contexts. Deploy/Start Dependencies: These determine which channels are dependent on this one, and also which channels are dependencies for this one. This way you can have some channels deploy and start before others. Attachment Handler: This allows you to extract pieces of any incoming message and store them separately. As a message processes through a channel, multiple copies of it will be held in memory at once (for the raw / transformed / encoded versions of a message). Attachments are stored only once, so by using them you can greatly reduce your channels' memory footprint. Message St

JMS Listener

Recommendations

JMS Sender

Web Service Listener

HTTP Listener

Library Resources

Batch Processing

General Channel Properties

JMS Listener

JMS Sender

Web Service Listener

HTTP Listener

Library Resources

Batch Processing

General Channel Properties