The FTP Transport related properties like the address, firewall related
properties are settable when I create a static port using BizTalk
explorer.

However, when I try to create a dynamic port, I am only able to access FTP
parameters like the user name and password.

I am not able to set the Firewall parameters programmatically (in an
orchestration)... How do I set these properties programmatically??

[ Post a follow-up to this message ]

To the best of my knowledge what you attempt is not possible


Yossi Dahan

"rejoyin" <anonymous@discussions.microsoft.com> wrote in message
 news:ac202b6991a2c3226b32bc0b1f590fd8@lo
calhost.talkaboutsoftware.com...
>
> The FTP Transport related properties like the address, firewall related
> properties are settable when I create a static port using BizTalk
> explorer.
>
> However, when I try to create a dynamic port, I am only able to access FTP
> parameters like the user name and password.
>
> I am not able to set the Firewall parameters programmatically (in an
> orchestration)... How do I set these properties programmatically??
>
>
>
>

[ Post a follow-up to this message ]

No Yossi! dont tell me that.

Okay, let me explain you all the scenario. someone may have some thoughts
to enlighten me.

well, I am have to send some documents to different clients. My
organisation is having a firewall. Moreover, each of the end-client ftp
sites will be having their own firewalls. so in this case, I have to some
how programmatically dynamically set my authentication parameters inside
the orchestration. Or else, do you have any other idea to workaround?

Rejoy.

[ Post a follow-up to this message ]

use a role link in your orchestration and set the destination party before
sending. Then setup parties in biztalk explorer and assign send ports to
them.  This way you statically define the send ports with all hte proxy
information, and just have to dynamically figure out who you are sending to.
This keeps the transport related specifics out of your orchestration and in
the configuration where it belongs.

Matt


"rejoyin" <anonymous@discussions.microsoft.com> wrote in message
 news:96cb742e509fcfc1579cea40864276ed@lo
calhost.talkaboutsoftware.com...
> No Yossi! dont tell me that.
>
> Okay, let me explain you all the scenario. someone may have some thoughts
> to enlighten me.
>
> well, I am have to send some documents to different clients. My
> organisation is having a firewall. Moreover, each of the end-client ftp
> sites will be having their own firewalls. so in this case, I have to some
> how programmatically dynamically set my authentication parameters inside
> the orchestration. Or else, do you have any other idea to workaround?
>
> Rejoy.
>

[ Post a follow-up to this message ]

I guess a better approach is to have a send port configured per client.
then use content based routing to deliver the message from the orchestration
to the correct send port.
This way each port will be configured pre client.
it also means that if a client changes its configuration you don't have to
recompile, just change configuration.

Yossi Dahan


"rejoyin" <anonymous@discussions.microsoft.com> wrote in message
 news:96cb742e509fcfc1579cea40864276ed@lo
calhost.talkaboutsoftware.com...
> No Yossi! dont tell me that.
>
> Okay, let me explain you all the scenario. someone may have some thoughts
> to enlighten me.
>
> well, I am have to send some documents to different clients. My
> organisation is having a firewall. Moreover, each of the end-client ftp
> sites will be having their own firewalls. so in this case, I have to some
> how programmatically dynamically set my authentication parameters inside
> the orchestration. Or else, do you have any other idea to workaround?
>
> Rejoy.
>

[ Post a follow-up to this message ]

thanks for the suggestion yossi. i am working on this. 

[ Post a follow-up to this message ]