SOAP Adapter and Filename

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › SOAP Adapter and Filename

Viewing 1 reply thread
  • Author
    Posts
    • June 9, 2006 at 2:41 AM #14829
      community-content

        I cannot retain the original filename while send file through a web service.

        I did a simple test:

        -A simple schema in an assembly deployed to my BTS Server
        -A one-way webservice published from that schema and at the same time, let the wizard created a SOAP receive port
        -created a FILE send port subscribed to that SOAP receive port
        -Add the webservice reference in another biztalk project and send file to webservice from that project

        When i define the receive file to be %MessageID%.xml in the FILE send port, everything is fine. But when i changed the macro to be %SourceFileName%, the output file’s name is not set to be the original filename, it’s just a file called %SourceFileName%.

        Is that because SOAP adapter doesn’t keep the message context property(such as ReceivedFileName)?

        Any suggestions to deal with it?

        Thx.

      • June 16, 2006 at 4:17 AM #14830
        community-content

          I may try this to get the filename through WS:
          ===================================
          create one custom pipeline on SOAP send side — promote the context property \”ReceivedFileName\”

          Create a schema for SOAP Header, only inclued one element \”Filename\”.
          Create SOAP Header based on this schema using the wizard.

          Having another custom pipeline on SOAP receive side — take the value out of soap header and throws back to promoted proptery

          ===================================
          But i don’t know how to store the promoted property value into SOAP Header while submit file to WS. Or maybe i have to set up orchestration?

          Is the direction i’m going right?

          Thanks
          Merry

          • June 9, 2006 at 7:31 AM #14831
            community-content

              That is correct.
              None of the adapters propagate the message context. Once the message leaves the adapter the message context no longer exists.

              The SOAP receive port does not have the filename, that was left behind at the SOAP send adapter

              You have two options add a filename field to your message or use custom SOAP headers to pass the filename.

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