If your messages are in XML, you can use either the XML Wire Format in the MRM domain, or one of the XML domains (XML or XMLNS).
You are recommended to model your XML messages using the MRM domain, for the following reasons:
For example, you might have a data field that is rendered as an XML element in one message, and as an XML attribute in another message. Or you could have a data field that is known by a particular name in one message, and a different name in another message. This advanced rendering can be specified using XML Wire Format properties.
For example, if you have a message that is created by a legacy COBOL application, you can use an XML Wire Format to easily and quickly define the equivalent XML message. And you can create your message model by importing your COBOL copybook.
For example, the dictionary indicates the real data type of a field in the message, instead of always treating it as a character string. It also enables the MRM parser to validate XML messages against the dictionary. This provides similar capabilities to those offered by XML validation against an XML DTD or Schema.
Related Concepts
Message modeling concepts
Why model messages?
The MRM domain
The XML domains
The message model
Physical formats in the MRM domain
Related Tasks
Developing message models
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad10530_ |