JMS Connection
JMS Connection is the resource every other JMS activity points at. It holds the broker address, the credentials used to authenticate, the ConnectionFactory the provider client needs, and the TLS settings that secure the transport.
A connection reaches the broker one of two ways. Direct broker URL connects to the address in Broker URL using the ConnectionFactory class you select. JNDI looks the ConnectionFactory up through a separate JNDI resource instead.
The resource has three tabs: Configuration, Advanced, and TLS.
Configuration
| Field | Required | Description |
|---|---|---|
| Name | Optional | Name of the resource. |
| Description | Optional | Description of the resource. |
| Broker URL | Optional | Direct JMS broker URL, for example tcp://host:61616 or ssl://host:61617. Mapping and vault values are supported. |
| Username | Optional | Broker user. Mapping and vault values are supported. |
| Password | Optional | Broker password. Mapping and vault values are supported. |
Advanced
| Field | Required | Description |
|---|---|---|
| Client ID | Optional | Required for durable topic subscriptions; must be unique per connection. |
| Connection Mode | Optional | Direct broker URL or JNDI. Defaults to Direct broker URL. |
| ConnectionFactory Class | Optional | Direct mode only. Select a known JMS ConnectionFactory or type a provider-specific class name. The provider client jar must be available to the engine. |
| JNDI Resource | Optional | JNDI context resource used to look up the ConnectionFactory. |
| Connection Factory | Optional | JNDI name of the ConnectionFactory, for example ConnectionFactory or jms/CF. |
ConnectionFactory Class
ConnectionFactory Class applies in direct mode only, and defaults to ActiveMQ Artemis. The field accepts a provider-specific class name as well as the listed options.
| Provider | Class |
|---|---|
| ActiveMQ Artemis | org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory |
| ActiveMQ Classic | org.apache.activemq.ActiveMQConnectionFactory |
| IBM MQ | com.ibm.mq.jms.MQConnectionFactory |
| TIBCO EMS | com.tibco.tibjms.TibjmsConnectionFactory |
| Qpid JMS / AMQP 1.0 | org.apache.qpid.jms.JmsConnectionFactory |
Whichever you choose, the provider's client jar must be available to the engine.
JNDI mode
Set Connection Mode to JNDI to resolve the ConnectionFactory through a directory
rather than instantiate it directly. JNDI Resource selects the context to look up
through, and Connection Factory is the bound name to look up within it.
TLS
| Field | Required | Description |
|---|---|---|
| Enable TLS | Optional | Turns on the TLS settings below. Defaults to cleared. |
| Broker Trust Certificate | Optional | Certificate resource used to validate the JMS broker. |
| Client Certificate (mTLS) | Optional | Certificate resource containing the client certificate and private key used for mutual TLS. |
| Enabled Protocols | Optional | TLS protocol versions permitted for this connection: TLS 1.3, TLS 1.2, or both. Defaults to both. |
| Trust All Certificates (unsafe) | Optional | Disables broker certificate validation. Defaults to cleared. |
| Verify Broker Hostname | Optional | Verifies that the broker certificate matches the hostname in Broker URL. Defaults to selected. |
Trust All Certificates (unsafe) disables broker certificate validation entirely. Use it only for local troubleshooting; never enable it in production. Leave Verify Broker Hostname enabled in production — disable it only when using a certificate whose SAN does not contain the configured hostname or IP.