Connect to JMS

Name of the connection.

Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,

Maximum length is 255 characters.

Description of the connection. Maximum length is 4000 characters.

Stores sensitive credentials for this connection in the secrets manager that is configured for your organization.

This property appears only if secrets manager is set up for your organization.

This property is not supported by Data Ingestion and Replication.

When you enable the secret vault in the connection, you can select which credentials that the Secure Agent retrieves from the secrets manager. If you don't enable this option, the credentials are stored in the repository or on a local Secure Agent, depending on how your organization is configured.

For information about how to configure and use a secrets manager, see Secrets manager configuration.

The name of the runtime environment where you want to run tasks.

Select a Secure Agent, Hosted Agent, or serverless runtime environment.

Hosted Agent is not applicable for mappings in advanced mode.

Select Secure Agent for Streaming Ingestion and Replication.

For example, in IBM MQ it is the directory location that contains the .bindings file.

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 org.apache.activemq.jndi.ActiveMQInitialContextFactory

For more information, see the documentation of the JMS provider.

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.

For example, jms/QCF or jmsSalesSystem.