Re: Common SendPort - how should i define

[Eric Stott]

1. For each Port define it's own SendPort ?
For each logical port (port inside of an orchestration) you define a
physical port (port defined in the Administration Console): No, I would
define a single physical port and point all orchestrations to that send
port. I would define that send port in one application and then all of your
other orchestration's applications reference that 'parent' application and
then you bind it to that single send port.

Drawbacks, if you have to change the destination format, you have to change
all of the orchestrations (which you would have to do regardless of how it
is set up anyway)

Eric
http://blog.biztalk-info.com

"Amit M" <Am...@discussions.microsoft.com> wrote in message
news:F12ECDF4-549C-4A17...@microsoft.com...
> Hi,
>
> Let me descibe you the following scene,
>
> You have several applications each application contains several SendPorts,
> Most of sendport locations are reffer to the same target (let's say DB).
>
> how would you define your SendPort
>
> 1. For each Port define it's own SendPort ?
> 2. Define 1 SendPort for each Application , All ports reffer to it ?
> 3. Define a common application with 1 SendPort , All the Applicatins are
> reference to it ?
>
>
> Is there any side efect with each of the configuration ?
>
>
> Thanks for advanced
> Amit.
>

[Pedro Moreira]

I would define one single port that all applications refer to.
For that to work, all applications using this port would need to have a
reference to this "common" application. This can be easily done with the
Admin console.

Keep in mind that if this common application has resources that other
applications use (e.g. schemas,pipelines,etc) your deployment efforts greatly
increase.
You would need to undeploy the common application before redeploying any of
the other applications (as they have a reference to this common application)

Good luck

--
Pedro Moreira
BizTalk Consultant
Comparative Advantage Ltd
www.comparative-advantage.co.uk