Manipulating messages in the MRM domain

Find out 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.

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 look at the information in the following topic:
The following diagram shows the structure of the message, Customer, that is used in the following sample: The message is used in the samples in the topics listed previously to show ESQL that manipulates the objects that can be defined in a message model. You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.
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 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.

The video sample has three message definition files:
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
Look at the video rental message structure sample for detailed information about the objects that are defined in this message model: You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.
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
Manipulating message body content
Accessing objects in migrated message models
Related reference
ESQL reference
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:23

ac17180_