The following tables list WebSphere MQ message formats, and the settings
for particular properties, for the different types of messages exchanged by
the connector framework and the integration broker.
MQMD | Contains no relevant information. |
RFH2 message header | In the <mcd> folder, the following fields contain information that
identifies the message, its format, and how it needs to be parsed:
|
Message body | Contains an XML instance document that conforms to the XML schema and the imported message set definition for the business object specified by the message type in the RFH2 header. |
MQMD | Reply-to information is located in two fields: ReplyToQ and ReplyToQMgr. They contains the queue name and queue manager name to which the integration broker needs to direct the response message. In JMS messages, these fields specify the JMSReplyTo destination on the request message. MessageID (JMSMessageID) contains a unique value, which is copied to the CorrelID property field on the response message. |
RFH2 message header | In the <mcd> folder, the following fields contain information that
identifies the message, its format, and how it needs to be parsed:
In the <jms> folder, the Rto (JMSReplyTo) field contains a URI that encodes the queue name and queue manager name to which the integration broker needs to direct the response message. See WebSphere MQ: Using Java for information about how this URI is specified. The reply-to information in Rto and in ReplyToQ/ReplyToQMgr in the MQMD are the same. |
Message body | Contains an XML instance document that conforms to the XML schema and the imported message set definition for the business object specified by the message type in the RFH2 header. |
MQMD | The CorrelID field contains the message ID of the request to which the integration broker is responding. For JMS messages, this field is used to define JMSCorrelationID. |
RFH2 message header | In the <mcd> folder, the following fields contain information that
identifies the message, its format, and how it needs to be parsed:
In the <usr> folder, the following fields contain return status information:
|
Message body | Contains an XML instance document that conforms to the XML schema and the imported message set definition for the business object specified by the message type in the RFH2 header. |
MQMD | Reply-to information is located in two fields: ReplyToQ and ReplyToQMgr. They contains the queue name and queue manager name to which the integration broker needs to direct the response message. In JMS messages, these fields specify the JMSReplyTo destination on the request message. If the ReplyToQ and ReplyToQMgr fields are left blank, the connector framework is not expected to provide a response. If a response is required, messages can also specify reply-to information in the Rto property field of the message header. MessageID (JMSMessageID) contains a unique value, which is copied to the CorrelID property field on the response message. |
RFH2 message header | In the <mcd> folder, the following fields contain information that
identifies the message, its format, and how it needs to be parsed:
|
Message body | Contains an XML instance document that conforms to the XML schema and the imported message set definition for the business object specified by the message type in the RFH2 header. |
MQMD | The CorrelID property field contains the message ID of the request to which the connector framework is responding. |
RFH2 message header | In the <mcd> folder, the following fields contain information that
identifies the message, its format, and how it needs to be parsed:
|
Message body | Contains an XML instance document that conforms to the XML schema and the imported message set definition for the business object specified by the message type in the RFH2 header. |
MQMD | Contains no relevant information. |
RFH2 message header | In the <mcd> folder, the following fields contain information that
identifies the message, its format, and how it needs to be parsed:
|
Message body | See Appendix C, Connector startup options for information about message body content. |
MQMD | If the administrative message is Stop Connector, the Format property is set to: MQC.MQFMT_STRING and the Expiry (JMSExpiration) property field is set to one minute. |
Message body | See Appendix C, Connector startup options for information about message body content. |