A message set is a container for grouping messages and associated message resources (elements, types, groups).
A message set is a folder in a message set project that contains a messageSet.mset file. The name of the folder is the name of the message set. A message set project can contain just one message set.
A message set is created whenever you create a new message set project. If you already have an empty message set project, you can create a message set in it using the New Message Set wizard.
You can base your new message set on an existing message set. If you do so, all the definitions in the existing message set are copied into the new message set.
Resources within a message set are created as files, and are displayed under the message set folder in the Navigator view:
There is always one, and only one, messageSet.mset file in a message set. It contains message model properties that are common to all the content of the message set. It is also where you define the physical formats that you want for this message set. These can be Custom Wire Format (CWF), XML Wire Format (XML) and Tagged Delimited String Format (TDS).
The file is created for you when a new message set is created, and you manipulate its content with the Message Set Editor.
You can have many message definition files in a message set. Each file contains the logical model and associated physical model in XML Schema form for a group of related messages. See Message definition files and Ways to create message definitions.
These files are optional. You can have many message category files in a message set. A message category provides another way of grouping your messages, perhaps for documentation purposes or to assist with generating Web Services Description Language (WSDL) files. See Message categories.
When you have completed the resources in your message set, you can generate the message set in a form that can be used by an application. This could be:
As well as having a name, provided by the folder, a message set also has an identifier. This is a generated string of 13 characters that uniquely identifies the message set. You can use either the name or the identifier interchangeably whenever you need to specify the message set to a runtime product such as WebSphere Business Integration Message Broker (for example, in an MQRFH2 message header).
Although the name is more readable, the identifier is guaranteed to be unique and is intended for use where you do not have control over the names of the message sets you are using.
You can have as many message definition files as you want within one message set. But you are recommended to limit your message sets to a few related message definition files that share the same physical formats. There are several reasons for this:
So for example, if you have an XML message and an unrelated CWF message in the same message set, then both XML and CWF physical format properties will be present for all objects. But the XML properties are of no interest to the CWF message and so will take default values in that message. (Similarly, the CWF properties are not of interest to the XML message.) This can result in unwanted task list warnings.
So if you are modeling XML messages that have a recursive structure, you must ensure that recursive XML messages do not share a message set with non-XML physical formats.
MQWIH | WebSphere MQ work information header |
MQCIH | WebSphere MQ CICS bridge header |
MQRFH | WebSphere MQ rules and formatting header |
MQRFH2 | WebSphere MQ rules and formatting header - version 2 |
MQDLH | WebSphere MQ dead letter header |
MQSAPH | WebSphere MQ link for R/3 header |
MQMD | WebSphere MQ message descriptor |
MQIIH | WebSphere MQ IMS information header |
SMQ_BMH | WebSphere MQ link for R/3 bad message header |
MQMDE | WebSphere MQ message descriptor extension |
MQRMH | WebSphere MQ message reference header |
MQCFH | WebSphere MQ programmable command formats header |
Related Concepts
The message model
Message set projects
Message definition files
Message categories
Physical formats in the MRM domain
Related Tasks
Developing message models
Creating a message set project
Deleting a message set project
Adding a Custom Wire Format (CWF)
Adding an XML wire format
Adding a Tagged/Delimited String (TDS) wire format
Removing a physical format
Related Reference
Message Set editor
Message set properties
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad10320_ |