The MIME domain is the message domain that includes all messages that conform to the MIME standard.
The MIME domain that is implemented in WebSphere Message Broker supports the MIME formats in use in message-based applications, including SOAP with Attachments, and RosettaNet.
Use the MIME domain if your messages exploit the MIME standard for multipart messages. The MIME parser creates a logical tree in which each part of your original message is held as a separate BLOB. You can then parse the individual parts as required, using ESQL or a ResetContentDescriptor node.
The MIME parser is not a model-driven MRM 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. Therefore, you need 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 you can add this message definition to a message set using the New Message Definition File wizard. Import the appropriate MIME definition into a message set whose Message Domain property is MIME, and set up a project reference to this message set from your message flow project. The ESQL editor can then support code completion for MIME documents.