Manipulating messages in the MRM domain

If you have migrated message sets from WebSphere MQ Integrator Broker Version 2.1 or WebSphere MQ Event Broker Version 2.1, you might also need to refer to the information in the following section:

The following diagram shows the structure of the message, Customer, that is used in the Video Rental sample sample; it is used in the samples in the topics listed above to show ESQL that manipulates the objects that can be defined in a message model.


The message created by the Video sample, containing elements that define the customer and the video transaction

The message includes a variety of structures that demonstrate the ways in which metadata can be classified 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.

The video sample has three message definition files:
Customer.mxsd
Resides in the noTarget namespace
Address.mxsd
Resides in the namespace http://www.ibm.com/AddressDetails
Borrowed.mxsd
Resides in the namespace http://www.ibm.com/BorrowedDetails

Refer to the Video Rental message structure for detailed information about the objects that are defined in this message model.

Related concepts
Message flows overview
ESQL overview
Message modeling
Related tasks
Designing a message flow
Defining message flow content
Managing ESQL files
Developing message models
Related reference
Compute node
Database node
Filter node
ESQL reference