|
Home > Archive > BizTalk Server General > September 2005 > Port properties getting updated from BindingFile
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Port properties getting updated from BindingFile
|
|
| Pankaj 2005-09-09, 2:48 am |
| Hi All,
I am deploying an orchestration using a BindingFile.
The BindingFile contains the information about the two send ports and a
receive port used in the orchestration.
However, I have already created these ports using vbs script. The properties
of these ports are getting updated after deploying the orchestration using
the BindingFile.
However, I want to retain the properties of these ports and I dont want them
to be updated with the BindingFile information.
How do I achieve this?
What all changes do i need to make in the BindingFile?
Regards
Pankaj
| |
| Scott Colestock 2005-09-09, 5:52 pm |
| There is no reason you can't remove the definition of these physical ports
from your binding file if you have another means of creating them.
Scott Colestock
www.traceofthought.net
"Pankaj" <pankajml@aditi.com> wrote in message
news:f17e7e1fe8e142e9934b1d52a9ae2096@ur
eader.com...
> Hi All,
>
> I am deploying an orchestration using a BindingFile.
> The BindingFile contains the information about the two send ports and a
> receive port used in the orchestration.
>
> However, I have already created these ports using vbs script. The
> properties
> of these ports are getting updated after deploying the orchestration using
> the BindingFile.
>
> However, I want to retain the properties of these ports and I dont want
> them
> to be updated with the BindingFile information.
>
> How do I achieve this?
> What all changes do i need to make in the BindingFile?
>
> Regards
> Pankaj
| |
| Matt Milner 2005-09-09, 5:52 pm |
| I think the problem is that the ports need to be in the file to be
referenced by the orchestration binding information so they get properly
bound to the orchestration.
I'd say put the ports which are not bound to any orchestration in the
binding file as well, then use the StartSendPort.vbs script to start all of
your ports.
Matt
"Scott Colestock" <scolestock@community.nospam> wrote in message
news:uNyqyFUtFHA.2072@TK2MSFTNGP14.phx.gbl...
> There is no reason you can't remove the definition of these physical ports
> from your binding file if you have another means of creating them.
>
> Scott Colestock
> www.traceofthought.net
>
>
>
> "Pankaj" <pankajml@aditi.com> wrote in message
> news:f17e7e1fe8e142e9934b1d52a9ae2096@ur
eader.com...
>
>
| |
| Scott Colestock 2005-09-09, 5:52 pm |
| When <Service> elements in a binding file map logical ports to physical
ports (e.g. via ReceivePortRef elements, etc.) , the physical ports just
have to be present within the BizTalk environment - they don't have to be
defined in the same binding file.
Scott Colestock
www.traceofthought.net
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:OhoQkZUtFHA.1472@TK2MSFTNGP15.phx.gbl...
>I think the problem is that the ports need to be in the file to be
>referenced by the orchestration binding information so they get properly
>bound to the orchestration.
>
> I'd say put the ports which are not bound to any orchestration in the
> binding file as well, then use the StartSendPort.vbs script to start all
> of your ports.
>
> Matt
>
>
> "Scott Colestock" <scolestock@community.nospam> wrote in message
> news:uNyqyFUtFHA.2072@TK2MSFTNGP14.phx.gbl...
>
>
|
|
|
|
|