This provides a general introduction to the MIME parser and some of the restrictions in its use. The MIME domain does not support the full MIME standard, but is intended to support specific known uses of MIME.
MIME stands for Multipurpose Internet Mail Extensions. A multipart MIME message comprises a number of message parts, each qualified by MIME headers. The MIME domain and parser enable the user to parse and write multipart MIME messages.
MIME has historically been used to send e-mail messages. When e-mail attachments are involved, a multipart MIME message is used. Multipart MIME is becoming more widely used as a convenient physical format for sending other kinds of message that have attachments or consist of multiple separate parts. Examples are:
The MIME parser is bit stream driven and has no external metadata. It relies exclusively on bit stream metadata when parsing and on tree metadata when writing. The parser does not validate MIME messages against a message model and it ignores the tooling Validate property. The parts of a MIME message are handled as BLOBs. The user may choose to subsequently (re-)parse specific MIME parts using a different parser, and if this is an MRM parser, then they can be validated as usual. The MIME parser does not support on demand parsing and ignores the Parse Timing property.
The user can either specify the new MIME domain at runtime in an MQRFH2 header (WebSphere MQ only) or statically in their message flow in the tooling (on the input nodes: MQGet, HTTPRequest and ResetContentDescriptor). The MIME parser will then be invoked to own the last child of root (for example, the message body). The MIME domain can be specified with the ESQL CREATE PARSE clause and ASBITSTREAM function to parse and write bit streams. The MIME parser handles documents received both over the HTTP transport (where the Content-Type appears as an HTTP header) and over other transports (where the Content-Type header is part of the message body). In both cases, set the Content-Type value using the ContentType property in the MIME domain. Setting the Content-Type value directly in the MIME tree or HTTP trees can lead to the value being ignored or used inconsistently.
In practice it is expected that the MIME parser will handle the majority of uses of MIME in application-to-application messaging, including multipart MIME with a single part and non-multipart MIME documents.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad30600_ |