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
Start of change<jms>End of change
Start of changeJava Messaging ServiceEnd of change

Each folder is contained in a separate NameValueData field, each of which is preceded by a NameValueLength field.

Independent software vendors can choose other names for their folders. However, you can prefix your chosen folder name with their internet domain name to avoid naming conflicts and problems. For example, a vendor with domain name ourcompany.com might name its folders:
com.ourcompany.xxx  or  com.ourcompany.ourData

The mcd folder

The <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.
<Msd>
Message service domain
Valid values are:
mrm
Start of changeThe message is parsed by the MRM domain.End of change
xmlnsc
Start of changeThe message is XML and is parsed by the XMLNSC domain.End of change
xmlns
Start of changeThe message is XML and is parsed by the XMLNS domain.End of change
xml
Start of changeThe message is XML and is parsed by the XML domain.End of change
mime
Start of changeThe message uses the MIME standard and is parsed by the MIME domain.End of change
idoc
Start of changeThe message is a SAP ALE IDoc from the WebSphere MQ Link for R/3, and is parsed by the IDOC domain. End of change
none
The message is treated as an opaque BLOB, and delivered to the recipient without modification.

See Parsers for a description of each domain.

<Set>
The name of the message set containing the definition of the message.
<Type>
The name of the message type, within the specified message set, to which this message corresponds. The format of a simple message type is {namespace-uri}:name where name is the name of the message.

The format {namespace-uri}name (that is, with no colon) is also valid to maintain compatibility with previous versions of the WebSphere Event Broker product.

In Version 2.1, this element specifies an identifier, rather than a name, for the message type.

<Fmt>
The name of the MRM physical format, within the specified message set, to which this message corresponds.

In Version 2.1, this element specifies an identifier, rather than a name, for the MRM physical format.

The <Set> element is needed when <Msd> is mrm, xmlnsc, or idoc.

The <Type> element is needed when <Msd> is mrm.

The <Fmt> element is needed when <Msd> is mrm or idoc.

If an MQRFH2 header is present in an output message tree, an <mcd> folder is always added and populated. This is so that the MQRFH2 header accurately reflects the message template of the message. The <mcd> folder must not be removed from the MQRFH2 folder. If it is deleted - for example, by a Compute node - it is automatically added and populated again on exit from the node.

Tip: If this output message is sent to another message flow, the <mcd> folder in the MQRFH2 header takes precedence over the properties of the MQInput node in the receiving message flow. If you do not want this to happen, take one of the following actions:
  • In the receiving message flow, use a ResetContentDescriptor node after the MQInput node. This converts the input message to the required domain.
  • In the sending message flow, in a Compute node, serialize the message to a BLOB by using the following ESQL:
    SET OutputRoot.BLOB.UnknownParserName = '';
    SET OutputRoot.BLOB.BLOB = ASBITSTREAM(InputBody);

The psc folder

The <psc> folder is used to convey publish/subscribe command messages to the broker.

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 broker, 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 broker ignores this folder in messages that it receives from publish/subscribe applications.

The usr folder

The content model of the <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 should not occur more than once in a folder.
  • An MQRFH2 instance can contain, at most, one <usr> folder.
Start of change

The jms folder

The content model of the <jms> folder contains the following MQRFH2 JMS fields:
  • Dst - represents the JMSDestination header field.
  • Div - 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 on the content of JMS messages.

Related concepts
Parsers
Related reference
JMS message structure
End of change
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:41:03

aq06940_