JMS producer

Description

JMS producer sends each incoming row to a JMS queue or topic as a TextMessage.

It works with any JMS 3.0 provider — see JMS consumer for the broker notes, which apply equally here.

Rows are passed through unchanged, so the transform can sit in the middle of a pipeline rather than only at the end.

Option Description

Option	Description
Transform name	Unique name of the transform in the pipeline.
JMS connection	The JMS connection metadata object to use.
Destination type	`QUEUE` for point-to-point, `TOPIC` for publish/subscribe.
Queue / topic name	Name of the destination. Supports variables.
Use a JMS transaction	Commit each message in a JMS transaction instead of sending it outside one.
Message body field	Incoming field holding the message body. Required.
Correlation id field	Optional incoming field to set as the JMS correlation id, so replies can be matched back to the row that caused them.

Transform name

Unique name of the transform in the pipeline.

JMS connection

The JMS connection metadata object to use.

Destination type

QUEUE for point-to-point, TOPIC for publish/subscribe.

Queue / topic name

Name of the destination. Supports variables.

Use a JMS transaction

Commit each message in a JMS transaction instead of sending it outside one.

Message body field

Incoming field holding the message body. Required.

Correlation id field

Optional incoming field to set as the JMS correlation id, so replies can be matched back to the row that caused them.

The body field is read as a string using its Hop value metadata, so a non-string field is converted with the conversion mask configured on it.
A missing body or correlation id field fails the transform on the first row with the field name it looked for, rather than sending empty messages.