When you have put an instance of the MQReply node into a
message flow, you can configure it.
About this task
Configure the MQReply node as follows:
Procedure
- Optional: On the Description tab,
enter a short description, a long description,
or both.
You can also rename the node on this tab.
- On the Advanced tab:
- Select Segmentation
Allowed if you want IBM® MQ to break the message
into segments in the queue manager, when appropriate.
You must also set
MQMF_SEGMENTATION_ALLOWED
in
the MsgFlags field in the MQMD for segmentation
to occur.
- Choose the persistence mode that you want for the output
message.
- If you select Automatic (the
default), the persistence is as
specified in the incoming message.
- If you select Yes,
the message is put persistently.
- If you select No,
the message is put non-persistently.
- If you select As Defined
for Queue, the message
persistence is set as defined
in the IBM MQ queue.
- Choose the transaction mode that you want for the output
message.
- If you select Automatic (the
default), the message transactionality
is derived from how it was specified at the MQInput node.
- If you select Yes,
the message is put transactionally.
- If you select No,
the message is put non-transactionally.
- On the Validation tab, set the validation
properties; see Validation properties. If a message is propagated to
the Failure terminal of the node, it is not validated.
For more details, see Validating messages.
The
reply message is put (using MQPUT) to the queue
named in the input message MQMD as the ReplyTo
queue. You cannot change this destination.
What to do next
- Optional: connect the output terminals to another node. Connect
the Out or Failure terminal of this node to another
node in the message flow to process the message
further, process errors, or send the message to an additional
destination. If
you use aggregation in your message flows, you
must connect these output terminals.
- Optional: configure the MQReply node
for coordinated transactions; see Configuring MQ nodes for transactions.