Description of the IBM supplied messages
that you can import to create a new message definition file.
If the message is to be used with an XML parser,
the following points apply:
- If the message set to which you are adding the new message definition
file has an XML wire format layer, but does not have namespace support, the
imported IBM supplied message is modified to remove namespaces. Therefore,
enable namespace support before you import an IBM supplied message.
- If the message set to which you are adding the new message definition
file does not have an XML wire format layer, but has namespace support, only
the logical information appears in the model. The IBM supplied message is
not modified to remove namespaces. You can add the physical layer to the message
set before or after importing the IBM supplied message but you should add
the physical layer before you import an IBM supplied message.
- If the message set to which you are adding the new message definition
file does not have an XML wire format layer, and does not have
namespace support, only the logical information appears in the model and the
imported IBM supplied message is modified to remove namespaces.
The IBM supplied messages that you can import are:
- SOAP message definitions
- These model the SOAP-defined portions of SOAP XML messages and are best
used with the MRM, XMLNSC, or XMLNS parsers. The 'soapenv' definitions model
the SOAP envelope structure used to wrapper the user-defined body of a SOAP
message. The 'soapenc' definitions model certain structures for use in "rpc/encoded"
style SOAP messages. Separate definitions are supplied for versions 1.1 and
1.2 of the SOAP standard.
- Multipart MIME message definitions
- These model the MIME-defined portions of multipart MIME messages and should
be used with the message broker's MIME parser. Use the 'mime_multipart' definition
for normal multipart MIME messages such as SOAP with Attachments or RosettaNet.
Use the 'mime_nested_multipart' definition for multipart MIME messages where
the individual parts can themselves be multipart MIME, an example being S/MIME.
- SAP IDoc message definition
- This models the SAP-defined portion of an IDoc which precedes the user-defined
content. You must use it with the message broker's IDOC parser.
- TimeoutRequest message definition
- This models the TimeoutRequest message used in conjunction with the message
broker TimeoutControl and TimeoutNotification nodes. You can use it with any
parser.