The MIME domain implemented in WebSphere Message Broker does not support the full MIME standard, but does support the MIME formats in use in message based applications, including SOAP with Attachments and RosettaNet.
The MIME domain should be used if your messages exploit the MIME standard for multipart messages. The MIME parser will create a logical tree in which each part of your original message is held as a separate BLOB. The individual parts may then be further parsed as required using ESQL or a ResetContentDescriptor node.
Note that the MIME parser is not a model-driven parser,
but relies entirely on the bit stream metadata to create its logical tree.
Similarly when a MIME tree is written back to a bit stream, the MIME domain
relies on the structure and metadata of the tree itself. This makes it particularly
important to understand the mapping between the bit stream and the logical
tree, and its relationship to the ContentType property. To set
the Content-Type value use the ContentType property in the MIME domain.
A model of the MIME multipart message structure is available as an IBM supplied message definition, and may be added to a message set using the New Message Definition file wizard. This enables features in other editors, such as the WebSphere Message Broker ESQL editor code completion feature, to make use of MIME header fields.