%SourceFileName% with FTP Send Port

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › %SourceFileName% with FTP Send Port

Viewing 3 reply threads
  • Author
    Posts
    • October 19, 2006 at 2:03 PM #16133
      community-content

        Guys,

        I have an FTP send port that subscribes to a receive port.  When a file comes in through the receive port, the send port is supposed to FTP the same file to another location.  I am trying to persist the file name.  Under the "FTP Transport Properties", I did specify %SourceFileName% for the "Target File Name" field.  With this setup, nothing gets transferred over to the FTP site.  I don't even get any error message.  But if I change the "Target File Name" filed to something like "test.txt", it works fine.

         Does this mean %SourceFileName% doesn't work with an FTP Send Port?  If so, I probably have to use an orchestration with a dynamic port right? (I was hoping to avoid that).

         

        Thanks.

      • October 23, 2006 at 6:07 PM #16162
        community-content

          You might want to Stop your Send Port but leave it Enlisted.  Then, check out the message contact properties using HAT.  You are looking for File.ReceivedFileName.  That’s what controls the %SourceFileName% macro.  I thought it was there for FTP – but maybe not. 

           

          All you would need is a very simple pipeline component to promote your FTP files name into File.ReceviedFileName.  I think FTP has it’s own file name called http://FTP.ReceivedFileName or something.  That’s what you would need to set to File.ReceivedFileName.

           

          Make sense?

          • November 1, 2006 at 12:00 AM #16271
            community-content

              Hi Stephen,   how about for HTTP adapter in the send port..  how can i retain the original filename ?

               

              • November 1, 2006 at 6:41 PM #16282
                community-content

                  I don’t think you can get this information from the HTTP Adapter.  It doesn’t really have the concept of a file name.  You can look in the help guide under Message Contact Properties and see what HTTP has to offer.  But I don’t think anything will be a file name.

            • November 2, 2006 at 1:57 AM #16291
              community-content

                You have to promote the property FILE.ReceivedFileName in a custom pipeline, it is not promoted by default. Even if you use an orchestration you won't get the file name if it's not promoted on the FILE receive port…

              • November 2, 2006 at 7:57 AM #16297
                community-content

                  Hi,

                  How can we extract the Receive filename from a custom receive adapter in an orchestration?

                  • November 2, 2006 at 2:49 PM #16299
                    community-content

                      As far as I know, in any custom adapter you are responsible for setting any context properties yourself.  So if you want the file name you will need to promote it.

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