I am creating 2 data files (excel and a txt file) and these files do not hav
e
associated schema with it.

Does 2004 still allow me to FTP these files using the FTP adapter.

Thanks

Minaz

[ Post a follow-up to this message ]

Yes, the adapter works with streams of data and won't care what type they
are.  In an orchestration, you'll need to treat them as
System.Xml.XmlDocument.  When you send and receive files of this type, use
the pass through pipelines, or custom pipelines with no xml or flat file
assembler or disassembler.

Matt


"Minaz" <Minaz@discussions.microsoft.com> wrote in message
news:CB4DE828-87E9-4DB0-BEA8-8187070E8FA3@microsoft.com...
>I am creating 2 data files (excel and a txt file) and these files do not
>have
> associated schema with it.
>
> Does 2004 still allow me to FTP these files using the FTP adapter.
>
> Thanks
>
> Minaz

[ Post a follow-up to this message ]

Thanks for the reply.

But my files are on the disk in a particular folder and I have to FTP those
files to mainframe. This will be a part of the orchestration workflow though
.
Also I have to use a dynamic send port. When using a dynamic send port, I
have to associate the message properties to the  FTP username and password.

So how can I a create these files of XML document. And these files are also
big ~ 50 MB.

Do I get a sample code for this.

Thanks
Minaz

"Matt Milner" wrote:

> Yes, the adapter works with streams of data and won't care what type they
> are.  In an orchestration, you'll need to treat them as
> System.Xml.XmlDocument.  When you send and receive files of this type, use
> the pass through pipelines, or custom pipelines with no xml or flat file
> assembler or disassembler.
>
> Matt
>
>
> "Minaz" <Minaz@discussions.microsoft.com> wrote in message
> news:CB4DE828-87E9-4DB0-BEA8-8187070E8FA3@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Which message properties are you associating with hte user name and
password?  Any data from the original files?

You can use a file receive with the pass through pipeline and then inside
your orchestration you can still set message context properties such as hte
FTP username and password.  In your orchestration, the message type will be
System.Xml.XmlDocument.

you'll set the message properties for username and password like so:
OutboundMessage(FTP.UserName) = "someusername";
OutboudnMessage(FTP.Password) = "mypassword";

Matt


"Minaz" <Minaz@discussions.microsoft.com> wrote in message
news:721E416B-0AFE-419F-B13D-D28451A42B91@microsoft.com...[vbcol=seagreen]
> Thanks for the reply.
>
> But my files are on the disk in a particular folder and I have to FTP
> those
> files to mainframe. This will be a part of the orchestration workflow
> though.
> Also I have to use a dynamic send port. When using a dynamic send port, I
> have to associate the message properties to the  FTP username and
> password.
>
> So how can I a create these files of XML document. And these files are
> also
> big ~ 50 MB.
>
> Do I get a sample code for this.
>
> Thanks
> Minaz
>
> "Matt Milner" wrote:
> 

[ Post a follow-up to this message ]