# Client Connection: JMS

To configure and use a JMS client connection in Data Mover, complete the following steps:

1. **Obtain the JMS client libraries** for the JMS provider you plan to use, as Data Mover requires these libraries to support the JMS features described in [JMS Connector](/data-mover-1.21/transfer-protocols-and-connectors/jms-connector.md).
2. **Configure the selected JMS provider in Data Mover** using DOIM, following the instructions in the [How to... configure JMS client connection support via DOIM](/data-mover-1.21/how-to.../...-configure-jms-client-connection-support-via-doim.md) page.
3. **Configure the JMS client connection** as described below to:
   * send a file as a single JMS message or as a set of multiple JMS messages (*file‑to‑message*)
   * receive a file as either a single JMS message or a set of multiple JMS messages (*message‑to‑file*).

Some configuration parameters depend strictly on the JMS provider being used. In this documentation, examples are provided for the following providers:

* Oracle WebLogic Server 12.2.1.4.0
* Apache ActiveMQ 5.18.x

Fields marked with an asterisk (\*) are mandatory.

<table><thead><tr><th width="230">Properties</th><th>Description</th></tr></thead><tbody><tr><td><strong>STATUS</strong></td><td><p>Enable or disable the client connection. Possible values: </p><ul><li>Enabled (default) </li><li>Disabled</li></ul></td></tr><tr><td><strong>NAME *</strong></td><td>Name of the JMS connection you are creating. The maximum number of characters is 128. Blanks and the ' " | special characters are not supported.</td></tr><tr><td><strong>DESCRIPTION</strong></td><td>Description of the JMS connection you are creating. The maximum number of characters is 2048.</td></tr><tr><td><strong>USERNAME *</strong></td><td>Username to connect to the JMS server.</td></tr><tr><td><strong>PASSWORD *</strong></td><td>Password to connect to the JMS server.</td></tr><tr><td><strong>INITIAL CONTEXT FACTORY CLASS NAME *</strong></td><td>ActiveMQ<strong>:</strong><br>org.apache.activemq.jndi.ActiveMQInitialContextFactory.<br>WebLogic<strong>:</strong><br>weblogic.jndi.WLInitialContextFactory</td></tr><tr><td><strong>INITIAL CONTEXT FACTORY URL *</strong></td><td>Server endpoint to which Data One connects. <br>ActiveMQ<strong>:</strong><br>The URL starts with tcp, followed by the JMS server IP address and port.<br>Example: <br>tcp://10.20.1.17:61616.<br>WebLogic<strong>:</strong><br>The URL starts with t3, followed by the JMS server IP address and port. <br>Example:<br>t3://10.20.1.17:7001</td></tr><tr><td><strong>CONNECTION FACTORY JNDI NAME *</strong></td><td><p>ActiveMQ<strong>:</strong><br>activeMQ:ConnectionFactory.</p><p>WebLogic<strong>:</strong><br>Connection factory value configured on the server.</p></td></tr><tr><td><strong>CLIENTID</strong></td><td>Name that can be given to the client connection to identify it on the server side.</td></tr><tr><td><strong>INITIAL CONTEXT ENVIRONMENT</strong></td><td>Map containing the properties that depend on the JMS server, used for configuration connection of the client.</td></tr><tr><td><strong>MAX RETRIES *</strong></td><td>Maximum number of retries. If this field is empty or set to 0, no retries will be executed and the job will be set to Failed if the first attempt is not successful. A high value corresponds to a high number of retrying attempts.</td></tr><tr><td><strong>RETRY INTERVAL</strong></td><td>This field will appear only if you have set the maximum numbers of retries to 1 or greater.<br>Time (in seconds) waited before retrying executing a job. The lower the value, the more frequent the retrying attempts. If this field is empty or set to 0, no retries will be executed and the job will be set to Failed if the first attempt is not successful.</td></tr><tr><td><strong>CONFIGURATION TEST</strong></td><td><p>Use this section to test that the <strong>Cluster</strong> and the <strong>STENG</strong> are connected correctly. Select a <strong>Cluster</strong> and a <strong>STENG</strong> you want to test and click the <strong>TEST</strong> button. Data Mover <strong>automatically</strong> selects a Cluster and a STENG to test the connection. Note that a Cluster will be selected only if it is the only one available. </p><p>A message with a green check will confirm a successful connection. A message with a red exclamation mark will warn about an unsuccessful connection. The message also details the reason why the connection fails. </p><p>The connection might not be successful for different reasons, each of them depending on the configuration.</p></td></tr></tbody></table>

For AMQ, refer to the [JNDI Support](https://activemq.apache.org/components/classic/documentation/jndi-support) documentation page.

For WebLogic, refer to the [WebLogic JNDI](https://docs.oracle.com/cd/E13222_01/wls/docs103/jndi/jndi.html) documentation page.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.primeur.com/data-mover-1.21/transfer-protocols-and-connectors/client-connections/client-connection-jms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.