Message service folders
A number of folders are defined for use by WebSphere® MQ products.
- <mcd>
- Message content descriptor
- <psc>
- Publish/subscribe command
- <pscr>
- Publish/subscribe command response
- <usr>
- Application (user) defined properties
- <jms>
- Java™ Messaging Service
Each folder is contained in a separate NameValueData field, each of which is preceded by a NameValueLength field.
ourcompany.com
might name its folders: com.ourcompany.xxx or com.ourcompany.ourData
The mcd folder
<mcd>
folder can contain the
following elements that describe the structure of the message data
in a WebSphere MQ message. They are all
character strings, and are case sensitive.
- If there is no
<mcd>
folder, one is added, and theMsd
,Set
,Type
, andFormat
fields are populated with values that match the current domain and the current setting in the Properties folder. - If there is an
<mcd>
folder, theMsd
,Set
,Type
, andFormat
fields are overwritten with values that match the current domain and the current settings in the Properties folder.
<mcd>
folder, you can remove
the header by using the following ESQL code with a Compute node: CALL CopyEntireMessage();
DELETE FIELD OutputRoot.MQRFH2.mcd;
PROPAGATE FINALIZE NONE; -- Propagate the message without updating the headers
RETURN FALSE; -- Ensure that the message is not propagated again.
The psc folder
The <psc>
folder is used to convey publish/subscribe command messages to the integration
node.
Only one psc
folder is allowed in the NameValueData field.
See Command messages for full details.
The pscr folder
The <pscr>
folder is used to contain
information from the integration node, in response to publish/subscribe command messages.
Only
one pscr
folder is present in a response message.
See Broker Response message for full details.
The integration node ignores this folder in messages that it receives from publish/subscribe applications.
The usr folder
<usr>
folder
has the following characteristics. - Any valid XML name that does not contain a colon can be used as an element name.
- Only simple elements, not groups, are allowed.
- All elements take the default type of string.
- All elements are optional, but must not occur more than once in a folder.
- An MQRFH2 instance can contain, at most, one
<usr>
folder.
The jms folder
<jms>
folder
contains the following MQRFH2 JMS fields:Dst
- represents the JMSDestination header field.Dlv
- represents the JMSDeliveryMode header field.Exp
- represents the JMSExpiration header field.Pri
- represents the JMSPriority header field.Tms
- represents the JMSTimestamp header field.Cid
- represents the JMSCorrelationID header field.Rto
- represents the JMSReplyTo header field.
See JMS message structure for more information about the content of JMS messages.