JMS Sender

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.
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	Template	${message.encodedData}	The actual payload to send to the JMS broker. By default the encoded data of this destination will be used. Velocity Variable Replacement is supported here.
M	Connection Templates		This section allows you to save the current state of your JMS Sender properties into a template, which may then be restored later if you make changes, or may also be applied to other JMS Sender connectors. More information here: JMS Listener

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

TCP Sender

This destination connector opens a new TCP client connection and sends messages over it. You can decide whether to keep a connection open, and if so for how long. Configurable transmission modes allow you to decide how to send outbound messages and receive responses. Supported property groups: Destination Settings Item Name Default Value Description A Transmission Mode MLLP The transmission mode determines how to send message data out on the socket byte stream, and how to receive responses. For additional information, see TCP Listener B Sample Frame <VT> <Message Data> <FS><CR> This is dependent on the Transmission Mode and displays an example of how an outgoing message frame is expected to look. C Mode Client Client: The TCP Sender will initiate new connections outbound to a remote server, and then send messages outbound on that connection. Server: The TCP Sender will open a server socket and listen for incoming connections. If queuing is enabled, messages will continue to queue until

Mirth® Connect by NextGen Healthcare User Guide

Database Writer

This destination connector connects to an external database and performs an INSERT/UPDATE statement (or any other statement, like calling a stored procedure). This can be done using a SQL statement, or by using JavaScript mode to execute the statement manually. The database connection will automatically be kept open across multiple dispatches. Supported property groups: Destination Settings Item Name Default Value Description A Driver Specifies the type of database driver to use to connect to the database. The following values are supported by default: Sun JDBC-ODBC Bridge MySQL Oracle PostgreSQL SQL Server / Sybase SQLite Additional drivers can be added by editing the dbdrivers.xml File. B URL The JDBC URL to connect to the database with. This is not used when "Use JavaScript" is checked. However, it is used when the Generate Connection / Insert feature is used to generate code. Use the Insert URL Template button to populate the URL field with a starting template. C Username The usern

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

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

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 Sender

Recommendations

JMS Listener

TCP Sender

Database Writer

Library Resources

Channel Properties

General Channel Properties

JMS Listener

TCP Sender

Database Writer

Library Resources

Channel Properties

General Channel Properties