Message Sets: IBM supplied messages that you can import

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 physical 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 physical format layer, but has namespace support, only the logical information is displayed in the model. The IBM supplied message is not modified to remove namespaces. Add an XML physical format to the message set 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 physical 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 message definitions model the SOAP-defined portions of SOAP XML messages. They are best used with the SOAP parser. The definitions Soap 1.1 Envelope and Soap 1.2 Envelope model the SOAP envelope structure that is used to wrapper the user-defined body of a SOAP message. The definitions Soap 1.1 Encoding and Soap 1.2 Encoding model certain structures for use in "rpc/encoded" style SOAP messages.

An IBM message for the SOAP domain tree is supplied as a schema that provides content-assist in creating a logical model for the SOAP domain by using the ESQL or mapping editor.

Multipart MIME message definitions

These message definitions model the MIME-defined portions of multipart MIME messages and must be used with the message broker's MIME parser. Use the MIME multipart header definition for typical multipart MIME messages such as SOAP with Attachments, or RosettaNet. Use the MIME Nested Multipart header definition for multipart MIME messages in which the individual parts can themselves be multipart MIME; for example, S/MIME.

SAP IDoc message definitions

These message definitions model the SAP-defined portion of ALE and File IDocs that precede the user-defined content. The ALE IDoc model can be used with the MRM and IDOC parsers. The File IDoc model can be used with the MRM parser only.

Timeout Request message definition

This message definition models the TimeoutRequest message that is used in conjunction with the message broker TimeoutControl and TimeoutNotification nodes. You can use it with any parser.

CSV message definition

This message definition models a CSV (comma separated value) format message. It can be used with the MRM parser.