Mike,
MIME (Multipurpose internet mail extension) is a message protocol. You can find out more in RFC 2045.
WM does provide the tools to parse an incoming MIME message without the RNIF adapter.
My company had a need to do this. We basically specified a custom protocol for transferring data, because our clients wanted something “lighter” than an RNIF pip. We ended up using SOAP with Attachments, which happens to also use MIME as the message protocol.
We therefore had to code all the parsing of the MIME, validation of the SOAP headers etc…
As an aside - I don’t think what we implemented with SOAP is any lighter than an RNIF message - its basically the same thing. MIME structure with xml in the body parts and optionally attachments in some form of encoded binary form.
But as RMG said before, it is much easier to use the RNIF adapter, especially since you want to implement an RNIF pip. We also use the RNIF adapter in production and currently have had no problems with the CM.
#B2B-Integration#webMethods#Integration-Server-and-ESB