JMS Sender
JMS Sender publishes a message to a queue or topic through the selected JMS Connection. It sends and returns; it does not wait for a response. To send a request and wait for a correlated reply, use JMS Request Reply instead.
The payload is mapped on the Input tab and serialized according to Message Type. Standard JMS headers and custom application properties are set from the input as well.
The activity has four tabs: Configuration, Advanced, Input, and Output.
Configuration
| Field | Required | Description |
|---|---|---|
| Name | Optional | Name of the component. |
| Description | Optional | Description of the component. |
| JMS Connection | Optional | The JMS connection resource to send through. |
| Destination Type | Optional | Queue or Topic. Defaults to Queue. |
| Destination Name | Optional | Direct physical queue or topic name by default. Enable Destination Name Is JNDI on the Advanced tab to treat this as a JNDI binding name resolved through the selected JMS Connection's JNDI resource. |
| Message Type | Optional | How the payload is serialized: Text, Byte, Object, Stream, or Map. Defaults to Text. |
| Input Properties Key | Optional | Input object holding custom JMS application property values. Defaults to properties. |
Advanced
| Field | Required | Description |
|---|---|---|
| Destination Name Is JNDI | Optional | When enabled, Destination Name is resolved from the JMS connection's JNDI context instead of used as a physical queue or topic name. Defaults to cleared. |
| Properties | Optional | Custom JMS application properties. These are separate from standard JMS headers and can be typed. |
Input
| Field | Data Type | Description |
|---|---|---|
| destinationName | String | Runtime destination override. When non-empty, this overrides the configured Destination Name; Destination Type and JNDI lookup remain controlled by the activity configuration. |
| payload | Any | Message payload sent as the JMS body. |
| messageHeaders | Object | Standard JMS headers to set as first-class fields. Overrides the config defaults. |
| properties | Object | Configured JMS application properties. These are user-defined JMS properties, separate from standard JMS headers. |
How payload is serialized follows Message Type. Text sends a plain string when
mapped from a string, or JSON text for objects and arrays. Map requires an object and
sends a JMS MapMessage. Byte, Object, and Stream serialize the mapped JSON value.
messageHeaders
| Field | Data Type | Description |
|---|---|---|
| correlationId | String | Sets JMSCorrelationID — echo a request's id to correlate a reply. |
| type | String | Sets JMSType. |
| priority | Integer | Send priority 0–9; applied at send time. |
| deliveryMode | Integer | JMSDeliveryMode: 1 is non-persistent, 2 is persistent. Applied at send time. |
Output
The activity returns a sendJMSMessageOutput object.
| Field | Data Type | Description |
|---|---|---|
| messageSent | Boolean | True when the message was sent to the JMS destination. |
| payload | Object | Decoded JMS payload. |
| messageHeaders | Object | Standard JMS headers plus configured and custom JMS properties. |
| properties | Object | Configured JMS application properties. |