Problems retrieving a Multi Part Message

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Problems retrieving a Multi Part Message

Viewing 1 reply thread
  • Author
    Posts
    • November 24, 2008 at 4:03 PM #21246
      community-content

         Hi,

         I’m having a problem receiving a multi part message.  I have tried a number of pipeline combinations, including a custom pipeline with a MIME component. 

        I have not been able to locate any examples that show receiving a multi-part message except via the SMTP adapter and I do not believe this is applicable to my situation.  The message is coming from a customer over HTTPS from a Ponton server (messaging application commonly used in the paper industry).  It is then being dropped to file before being picked up by the processing orchestration.

        Any suggestions would be appreciated.

        Sample Message:

        ——=_Part_4_17226044.1227209055965

        Content-Type: text/xml; charset=utf-8

        Content-Transfer-Encoding: binary

        Content-Id: <EbXml-Envelope-1227209055761>

         

        <?xml version=’1.0′ encoding=’UTF-8′?><soapenv:Envelope xmlns:soapenv=”http://schemas.xmlsoap.org/soap/envelope/”&gt;

        ….ebXML Header goes here……

        </soapenv:Envelope>

        ——=_Part_4_17226044.1227209055965

        Content-Type: text/xml

        Content-Transfer-Encoding: binary

        Content-Id: payload-1227209055761

        Content-Disposition: attachment;filename=”payload.xml”

         

        <?xml version=”1.0″ encoding=”UTF-8″?>

        <PurchaseOrder xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance&#8221; xsi:noNamespaceSchemaLocation=”PurchaseOrderV2R30″ PurchaseOrderStatusType=”Original” PurchaseOrderType=”StandardOrder”>

        ….PO XML goes here……

              </PurchaseOrder>

        ——=_Part_4_17226044.1227209055965–

         

      • November 24, 2008 at 5:29 PM #21247
        community-content

          You may need to write a custom MIME Decoder pipeline component.

          The standard MIME/SMIME Decoder scans the first 1024 bytes of the incoming message to search for the “MIME-Version” header. If this header is not found, the message is treated as a non-MIME message. The HTTP Adapter will strip off the HTTP headers before passing the message up the pipeline so you may lose the things like MIME-Version, etc

           

          • November 25, 2008 at 10:09 AM #21254
            community-content

               

              Thanks Greg for the response.  I was hoping to avoid a custom component but it is looking like it is the only option.

              Thanks again,

              Geordie

        • Author
          Posts
        Viewing 1 reply thread
        • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.