IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

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.

The structure of the "Customer" message is shown 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 information about samples only when you use the product documentation that is integrated with the IBM® Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration 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 Integration 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 information about samples only when you use the product documentation that is integrated with the IBM Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.


ac17180_.htm | Last updated Friday, 21 July 2017