JMS Connector Listen Activities¶

JMS Listen¶

A JMS Listen activity allows listening on a queue for messages. Messages are received by the JMS Listen activity asynchronously. A new message is only received once the processing of any prior message completes.

• Queue Name: The name of the queue to receive the messages from asynchronously. The queue name supports the use of project and global variables in its definition, allowing for dynamic configuration of the activity.
• Message Type: Supports TEXT and BYTE message types. Default type is TEXT. For messages of the BYTE type_,_ you need to apply the Jitterbit function Base64Decode() on the message payload in the Response Transformation.

For example, to write a message body to a file after decoding with the file name listen-binary.png:

<trans>
WriteFile("<TAG>Targets/Decode Binary Target</TAG>",
  Base64Decode(listenMessageResponse$payload$message.messageBody$),
  "listen-binary.png");
</trans>

For decoding text data stored as a byte array in a JMS queue:

<trans>
WriteToOperationLog(String(Base64Decode((listenMessageResponse$payload$message.messageBody$))));
</trans>

• Message Selector: __An expression used to filter the messages, by header field and property references. It cannot reference message body values. The syntax is based on a subset of the SQL92 conditional expression syntax. If the value of a message selector is an empty string, the value is treated as a null and indicates that there is no message selector for the message consumer. The message selector supports the use of project and global variables in its definition, allowing for dynamic configuration of the activity.
• Transacted Session: Allows creating of a transacted session, where the acknowledgment is sent when the session is committed. Default is TRUE.
• Acknowledge Mode: Supports either AUTO_ACKNOWLEDGE or DUPS_OK_ACKNOWLEDGE mode when Transacted Session is set to FALSE.