Message service folders

The following folder names 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

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, to avoid naming problems, we recommend that vendors prefix their chosen folder name with their internet domain name; 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
<Set>
Message set
<Type>
Message type
<Fmt>
Message format

The domain element identifies how to handle the message. The syntax of the other elements (set, type, and format) depend on the value assigned to <Msd>.

The following values for <Msd> have been allocated:
mrm
WebSphere Business Integration Message Broker MRM-managed messages.
This domain supports the following values for <Fmt>:
xml
XML representation
pdf
MTI bitstream representation
CWF identifier
The custom wire format identifier that you assigned to your message set

The Set element should contain the identifier of the MRM message set to which the message belongs; this identifier is obtained from the workbench.

The Type element value is the identifier of the MRM message definition, within the specified message set, to which this message belongs.

none
The message is treated as an opaque blob, and delivered to the recipient as is. If this domain is chosen, the set and type must not be specified.
xml
The message is treated as a self-defining XML message.
Note: Messages in the neonmsg domain are not compatible with messages in the neon domain.

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.

There is only one pscr folder 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 is as follows:
  • Any valid XML name can be used as an element name, providing that it doesn't contain a colon
  • Only simple elements, not groups, are allowed
  • All elements take the default type of string, unless modified by a dt="xxx" attribute
  • All elements are optional, but should occur no more than once in a folder
  • An MQRFH2 instance can contain no more than one <usr> folder