WebSphere Message Brokers
File: ad00790_
Writer: Terry Cowling

Concept topic

This build: July 31, 2007 21:21:40

MRM XML physical format

The MRM XML physical format describes the physical representation of an XML message for use by the MRM parser.

An XML wire format describes the physical representation of a message that is written according to the standards given in the W3C Extensible Markup Language (XML) specification. The wire format defines information that is used to parse or write XML messages in a runtime environment such as a broker. XML versions 1.0 and 1.1 are both supported.

You can add more than one XML physical format to a message set, but within that message set, each physical format must have a unique name. The default name for an XML wire format is XML1. Typically, you might do this if a single logical message can be represented with its components rendered in different ways, for example as the value of an element in one case but as the value of an attribute in another. The physical format name identifies the definitions that are to be used by the message broker at runtime.

After adding an XML physical format, all XML properties for all existing objects in the message set will be set to default values. Thus, immediately after adding the format and deploying the message set to a runtime environment, it is possible to process XML messages using MRM features.

You can configure XML properties for the message set, and for objects within the message set. Objects that can have XML properties are messages, elements, and attributes. For example, a message object can be customized to define a specific DTD declaration on output; an element can have a tag name assigned to it which is different from its MRM element name.

Adding an XML wire format to a message set allows you to both process input messages, and to construct output messages in this format. You can also transform messages between XML and either CWF or TDS.

XML messages are, by their nature, self-describing: each piece of data is prefixed by a tag name or an attribute name. Therefore, it is possible for an XML message instance to contain elements which are not in the MRM definition for that message.

Although it is possible to define an XML message using the Message Definition Editor, WebSphere Message Broker also provides importers for both XML Schema and DTD, and these are often quicker and easier than manual definition.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:21:40

ad00790_ This topic's URL is: