This topic show you how to deal with 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 on manipulating message body content,
see the related links.
The diagram below 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 above 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 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 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.