Skip to main content

Reply To Message

Reply To Message responds to a request that arrived through JMS Receiver. It is the responder half of a JMS request/reply exchange — the counterpart to JMS Request Reply on the requester side.

Where the reply goes is resolved in order: the input replyTo if set, otherwise the incoming request's replyTo header, otherwise the Reply Destination configured here. Mapping the receiver's output into requestMessage is what supplies the second of those, along with the correlation identifiers.

The activity has four tabs: Configuration, Advanced, Input, and Output.

Configuration

FieldRequiredDescription
NameOptionalName of the component.
DescriptionOptionalDescription of the component.
JMS ConnectionOptionalThe JMS connection resource used to send the reply.
Reply Message TypeOptionalHow the reply payload is serialized into the outbound JMS response message: Text, Byte, Object, Stream, or Map. Defaults to Text.
Reply DestinationOptionalUsed when the input replyTo is blank. For standard JMS request/reply, map replyTo from the receiver's jmsOutput.messageHeaders.replyTo, or configure a fixed reply destination here.

Advanced

FieldRequiredDescription
Fallback Reply TypeOptionalQueue or Topic. Defaults to Queue.
Correlate With Request Message IDOptionalIf the request has no JMSCorrelationID, set the reply JMSCorrelationID to the request JMSMessageID. Defaults to selected.
Acknowledge Source On ReplyOptionalAcknowledge the source message when the reply is sent. Defaults to selected.

Acknowledge Source On Reply applies only when the input contains a manual JMS ack token from JMS Receiver.

Input

FieldData TypeDescription
payloadAnyReply payload sent as the JMS body.
replyToStringReply destination override. When blank, the activity uses requestMessage.messageHeaders.replyTo, then the configured Reply Destination.
requestMessageObjectOriginal JMS request message metadata. Usually map the receiver's jmsOutput here.
replyMessageHeadersObjectStandard JMS headers to set on the outgoing reply. Usually leave blank; correlation is copied from requestMessage by default.

payload follows Reply Message Type: Text sends a plain string when mapped from a string, or JSON text for objects and arrays, and Map requires an object and sends a JMS MapMessage.

requestMessage

FieldData TypeDescription
ackTokenStringManual acknowledgement token from JMS Receiver when its mode is Manual / early acknowledge.
messageHeaders.replyToStringOriginal request JMSReplyTo destination. The reply is sent here when present.
messageHeaders.correlationIdStringOriginal request JMSCorrelationID. Reused on the reply when present.
messageHeaders.messageIdStringOriginal request JMSMessageID. Used as the reply JMSCorrelationID when correlationId is blank.

replyMessageHeaders

FieldData TypeDescription
correlationIdStringReply JMSCorrelationID override.
typeStringReply JMSType value.
priorityIntegerReply JMSPriority override.
deliveryModeIntegerReply JMSDeliveryMode override: 1 is non-persistent, 2 is persistent.

Output

The activity returns a replyToMessageOutput object.

FieldData TypeDescription
messageSentBooleanTrue when the message was sent to the JMS destination.
replyDestinationStringQueue or topic that received the reply.
payloadObjectDecoded JMS payload.
messageHeadersObjectStandard JMS headers plus configured and custom JMS properties.
propertiesObjectConfigured JMS application properties.