Connections > Connection properties > JMS connection properties

JMS connection properties

When you set up a JMS connection, you must configure the connection properties.
The following table describes the connection properties for the JMS connection:
Connection Name
Name of the connection.
The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters:
~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
Optional. Description that you can use to identity the connection.
The description cannot exceed 4,000 characters.
The JMS connection type.
If you do not see the connection type, go to the Add-On Connectors page to install the connector.
Runtime Environment
Name of the runtime environment where you want to run the tasks.
Connection URL
URL of the JNDI naming provider.
For example, in IBM MQ it is the directory location that contains the .bindings file.
User Name
Optional. User name to the connection factory.
Optional. The password of the user account that you use to connect to the connection factory.
JNDI Context Factory
The JMS provider specific initial JNDI context factory implementation for connecting to the JNDI service. This value is a fully qualified class name of the Initial Context Factory.
For example, the class name of the Initial Context Factory for ActiveMQ is
For more information, see the documentation of the JMS provider.
JNDI Package Prefixes
A colon-delimited list of package prefixes to use when loading URL context factories. These are the package prefixes for the name of the factory class that will create a URL context factory.
For more information about the values, see the documentation of the JMS provider.
JMS Connection Factory
The name of the object in the JNDI server that enables the JMS Client to create JMS connections.
For example, jms/QCF or jmsSalesSystem.
Note: Ensure to copy the external JMS JAR files to the following location:
After copying the external JMS JAR files, restart the Secure Agent.