|
Home > Archive > BizTalk Server Orchestration > June 2005 > Binding is not listed in Port Binding Properties dialog.
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 |
Binding is not listed in Port Binding Properties dialog.
|
|
|
| All,
Right click and Select bind on the Orchestration in Biz Talk Explorer.
Port Binding Properties dialog does not contain the Binding sectioin.
Please let us know why this is happening.
I am not able to figure out why this is happening. Please suggest a way if
you have experienced similar problem.
thanks in advance,
Srikanth
| |
| JGaska [http://www.IoniaSolutions.com] 2005-04-26, 5:49 pm |
| Srik;
Yup, I know exactly what you mean. If your orchestration has no bound ports
within the orchestration (Not including your initial receive port), the
binding section does not show up. Add an outbound file port to your
orchestration and deploy, you will see the binding show the name of the port
from within the orchestration and a drop down menu with a selection bound to
the name of the send port.
Let me know if you have any questions or you need a screen shot as an example.
-Joe
"Srik" wrote:
> All,
>
> Right click and Select bind on the Orchestration in Biz Talk Explorer.
> Port Binding Properties dialog does not contain the Binding sectioin.
> Please let us know why this is happening.
> I am not able to figure out why this is happening. Please suggest a way if
> you have experienced similar problem.
>
>
> thanks in advance,
> Srikanth
>
| |
| Don Keller 2005-06-24, 5:54 pm |
| help! I'm having the same problem. I had an orchestration deployed and it
was working fine. Then I decided to finally put the schemas and maps into
their own referenced project. I've redeployed the assemblies and now the
binding page doesn't give me any ability to bind ports. I tried as was
explained below, to simply add an additional port but still now luck.
My orchestration has an intial file location receive port and it also
interacts with a web service. I don't understand why a simply change like
moving my schemas to a separate BT project would have this affect. I've made
many other changes to this orchestration in the past and have deployed it
many times with no problem.
"JGaska [http://www.IoniaSolutions.com]" wrote:
[vbcol=seagreen]
> Srik;
>
> Yup, I know exactly what you mean. If your orchestration has no bound ports
> within the orchestration (Not including your initial receive port), the
> binding section does not show up. Add an outbound file port to your
> orchestration and deploy, you will see the binding show the name of the port
> from within the orchestration and a drop down menu with a selection bound to
> the name of the send port.
>
> Let me know if you have any questions or you need a screen shot as an example.
>
> -Joe
>
>
>
>
> "Srik" wrote:
>
| |
| JGaska [http://www.IoniaSolutions.com] 2005-06-24, 5:54 pm |
| Don;
In your WS port configuration wizard are you specifying now or specifying
later? Try changing the port to specify later and see if the page gives you
the ability. You should always specify later and use the XML config to bind
your port settings during deployment. Let me know how you are binding the WS
in the orch.
-Joe
"Don Keller" wrote:
[vbcol=seagreen]
> help! I'm having the same problem. I had an orchestration deployed and it
> was working fine. Then I decided to finally put the schemas and maps into
> their own referenced project. I've redeployed the assemblies and now the
> binding page doesn't give me any ability to bind ports. I tried as was
> explained below, to simply add an additional port but still now luck.
>
> My orchestration has an intial file location receive port and it also
> interacts with a web service. I don't understand why a simply change like
> moving my schemas to a separate BT project would have this affect. I've made
> many other changes to this orchestration in the past and have deployed it
> many times with no problem.
>
> "JGaska [http://www.IoniaSolutions.com]" wrote:
>
| |
| Don Keller 2005-06-24, 5:54 pm |
| Hi Joe,
Thanks for your quick response. In this case I had made a web reference in
the BizTalk project then added a port to my orchestration that had the Web
Port Type of the referenced web service. Based on your reply, I changed the
port to be specified later, deployed the project and there are still now
bindings available for my orchestration in the Explorer. All of this has
happened in my local development copy of BTS, I fortunately haven't
re-deployed this to our production BTS.
Thanks for the help.
Don
"JGaska [http://www.IoniaSolutions.com]" wrote:
[vbcol=seagreen]
> Don;
>
> In your WS port configuration wizard are you specifying now or specifying
> later? Try changing the port to specify later and see if the page gives you
> the ability. You should always specify later and use the XML config to bind
> your port settings during deployment. Let me know how you are binding the WS
> in the orch.
>
> -Joe
>
> "Don Keller" wrote:
>
| |
| Don Keller 2005-06-24, 5:54 pm |
| Sorry, there was a type-o in my previous post. "and there are still now
bindings" should be "and there are still NO bindings".
Thanks,
Don
"Don Keller" wrote:
[vbcol=seagreen]
> Hi Joe,
>
> Thanks for your quick response. In this case I had made a web reference in
> the BizTalk project then added a port to my orchestration that had the Web
> Port Type of the referenced web service. Based on your reply, I changed the
> port to be specified later, deployed the project and there are still now
> bindings available for my orchestration in the Explorer. All of this has
> happened in my local development copy of BTS, I fortunately haven't
> re-deployed this to our production BTS.
>
> Thanks for the help.
>
> Don
>
>
> "JGaska [http://www.IoniaSolutions.com]" wrote:
>
| |
| JGaska [http://www.IoniaSolutions.com] 2005-06-24, 5:54 pm |
| Cna you force the bindings using the Xml import tool and reference the orch
and the port? Does the orch allow you to start it without throwing an
exception? If it throws an exception then use the Xml import tool (you can
see how they do it in the samples which acompany BT). Basically if it throws
an exception then it is a UI bug, you should move to deployment scripts
anyway so if the Xml import works consider it a hint  . I never use the UI
for deployment I always use the tools for scripted deployment and bindings
and I always specify bindings in Xml files and configure locations based on
environment specific Xml config files for import.
"Don Keller" wrote:
[vbcol=seagreen]
> Sorry, there was a type-o in my previous post. "and there are still now
> bindings" should be "and there are still NO bindings".
>
> Thanks,
> Don
>
> "Don Keller" wrote:
>
| |
| Don Keller 2005-06-24, 5:54 pm |
| Do you happen to know what the name of the Sample is? I don't see one that
relates to that topic.
I now re-deployed the orchestration to my local machine using the XML
binding file from or production server, it created ports, etc, but I am
unable to then enlist and start the orchestration.
I wish I understood why BT would suddenly not show the ports that are
clearly configured in the Orchestration Designer, Ochestration View, etc.
Why would the Port Binding Properties have no knowledge of them?
This is really frustrating. I even took my old files (fortunately I backed
up my project prior to this modification) and deployed those and the same
issue is occurring. So it doesn't seem to be a related to how I have the
ports defined in the orchestration. Something else in BT would seem to be
causing the issue.
Any ideas Microsoft!!! I REALLY need to ultimately get this deployed to our
production server but am completely held up until I can resolve this on my
development machine.
Thanks again,
Don
"JGaska [http://www.IoniaSolutions.com]" wrote:
[vbcol=seagreen]
> Cna you force the bindings using the Xml import tool and reference the orch
> and the port? Does the orch allow you to start it without throwing an
> exception? If it throws an exception then use the Xml import tool (you can
> see how they do it in the samples which acompany BT). Basically if it throws
> an exception then it is a UI bug, you should move to deployment scripts
> anyway so if the Xml import works consider it a hint . I never use the UI
> for deployment I always use the tools for scripted deployment and bindings
> and I always specify bindings in Xml files and configure locations based on
> environment specific Xml config files for import.
>
>
> "Don Keller" wrote:
>
|
|
|
|
|