This topic describes additional fields added to the MQRFH2
header to allow for functions that can be used by service integration
but that are unavailable in WebSphere® MQ.
A set of message fields specific to the service integration
bus convey extra information not used in WebSphere MQ.
- These properties are inserted in the MQRFH2
header of application messages in the sib folder.
- These properties are inserted in the MQRFH2
header of application messages in the sib and jms folders.
They can be used to influence the routing of messages within
the service integration bus, but do not appear as JMS message fields
or properties.
MQRFH2 header and field (sib folder) |
SIBusMessage field or property |
Frp |
Forward routing path header field |
Rrp |
Reverse routing path header field |
RTopic |
Reply topic |
RPri |
Reply priority |
RPer |
Reply persistence |
RTTL |
Reply time to live |
MQRFH2 header and field (jms folder) |
SIBusMessage field or property |
Frp (appended to Dst field) |
Forward routing path header field |
Rrp (appended to Rto field) |
Reverse routing path header field |
MQRFH2 header and field (sib folder) |
SIBusMessage field or property |
RTopic |
Reply topic |
RPri |
Reply priority |
RPer |
Reply persistence |
RTTL |
Reply time to live |
When a message is sent to WebSphere MQ across a WebSphere MQ link, a sib folder is included
in the MQRFH2 header of the message if both of the following are true:
- The setting on the destination definition is configured to propagate
the MQRFH2 header.
- Fields corresponding to the sib folder content are set in the
message.