Accepts documents from upstream Snaps. Each input document is processed and sent as a message to the specified IBM MQ destination.

• Mapper
• Structure
• JSON Generator

Outputs a document for each successfully sent message containing message metadata including message ID and correlation ID.

• Filter
• Mapper
• JSON Formatter

Label

String

Required. Specify a unique name for the Snap. Modify this to be more appropriate, especially if more than one of the same Snaps is in the pipeline.

Default value: IBM MQ Producer

Required. The name of the IBM MQ queue or topic to which messages will be sent.

Example: TestQueue

Specify the type of destination to which messages are sent:

• Queue - Point-to-point message is published to one queue
• Topic - Publish-subscribe messaging where messages are published to multiple subscribers

Default value: Queue

When enabled, it creates a dynamic queue if it does not already exist. Dynamic queues based on a model queue (the model queue can be permanent or temporary).

Default value: Deselected

Specify the name of the model queue to use as a template for creating the dynamic queue. The model queue defines the attributes (such as maximum depth, message persistence, and access permissions). The model queue must be created or present in MQ. This field appears only when the Dynamic queue is enabled.

Example: SYSTEM.DEFAULT.MODEL.QUEUE

Specify the persistence mode for messages:

• As Queue Definition - Uses the persistence setting defined in the queue's configuration (MQPER_PERSISTENCE_AS_Q_DEF)
• Persistent - Messages are stored in persistent mode (MQPER_PERSISTENT)
• Not Persistent - Messages are stored are stored in non-persistent mode (MQPER_NOT_PERSISTENT)

Default value: As Queue Definition

Specify the MQMD property name.

Example: abc

Specify report options for the message. Accepts integer values or IBM MQ constant names.

Example: MQRO_EXCEPTION (reports exception messages)

Specify the message type indicator.

Example: 8 (for request messages)

Specify the message expiration time in tenths of a second. A value of -1 indicates no expiration.

Example: 600 (message expires after 60 seconds)

Specify the feedback code for report messages.

Specify the numeric encoding used for numeric data in the message.

Example: 273 (for big-endian integer encoding)

Specify custom properties as key-value pairs that are stored in the RFH2 (Rules and Formatting Header version 2) usr folder. These values are present in XML format in the <usr></usr> folder of RFH2.

Controls the message context (identity and origin information) that is set when the message is put on the queue:

• Default - No special context is set
• Set Identity Context - Sets identity context including UserIdentifier (MQPMO_SET_IDENTITY_CONTEXT)
• Set All Context - Sets all context fields including identity and origin information such as PutDate and PutTime (MQPMO_SET_ALL_CONTEXT)

Default value: Set All Context

Enables transaction coordination for put operations:

• Syncpoint - Messages are sent within a transactional unit of work. The transaction is committed when batch size is reached (MQPMO_SYNCPOINT)
• No Syncpoint - Messages are sent immediately without transactional control

Default value: No Syncpoint

Specify the number of messages to send per batch. This setting is particularly relevant when Syncpoint Control is enabled, as it determines how many messages are included in a single transactional unit of work.

Default value: 1

Example: 100 (sends 100 messages per transaction)

Specify the number of retry attempts for connection or network errors. When set to 0, the Snap does not retry on failure.

Default value: 0

Specify the wait time in milliseconds between retry attempts.

Default value: 1000

Example: 5000 (waits 5 seconds between retries)