See information about the latest product version
Manipulating messages in the MRM domain
How to use messages that have been modeled in the MRM domain, and that are parsed by the MRM parser.
The following topics show you how to deal with messages that have been modeled in the MRM domain, and that are parsed by the MRM parser. The physical formats associated with the message models do not affect this information unless specifically stated. Use this information in conjunction with the information about manipulating message body content; see Manipulating message body content.
- Accessing elements in a message in the MRM domain
- Accessing multiple occurrences of an element in a message in the MRM domain
- Accessing attributes in a message in the MRM domain
- Accessing elements within groups in a message in the MRM domain
- Accessing mixed content in a message in the MRM domain
- Accessing embedded messages in the MRM domain
- Accessing the content of a message in the MRM domain with namespace support enabled
- Querying null values in a message in the MRM domain
- Setting null values in a message in the MRM domain
- Working with MRM messages and bit streams
- Handling large MRM messages
You can view information about samples only when you use the information center that is integrated with the WebSphere® Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.

The message includes a variety of structures that demonstrate how you can classify metadata to the MRM. Within an MRM message set, you can define the following objects: messages, types, groups, elements, and attributes. Folder icons that represent each of these types of objects are displayed for each message definition file in the Broker Application Development perspective.
Each message definition file can contribute to a namespace; in this sample, each namespace is completely defined by a single message definition file. You can combine several message definition files to form a complete message dictionary, which you can then deploy to a broker.
- Customer.mxsd
- Resides in the no target namespace
- Address.mxsd
- Resides in the namespace http://www.ibm.com/AddressDetails
- Borrowed.mxsd
- Resides in the namespace http://www.ibm.com/BorrowedDetails
You can view information about samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.