|
Home > Archive > BizTalk Server General > May 2006 > Web Service call environment dependency...
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 |
Web Service call environment dependency...
|
|
|
| Dear All,
I'm currently calling multiple web services running on a remote machine
from my orchestration. Now that we have a new version of web service
code running on a seperate remote box I'm adding this new web service
references to my BizTalk project and pointing my ports to call this
instead of old, resulting in rebuilding my code. The signature of this
new web service version is same as the old one.
My doubt is, in future everytime my web service location is going to
change do I need to rebuild my code to reference this new web service
thru add web references or could I make use of binding files by
providing the url details for my SOAP adapter and just proceed. I do
understand that to execute web service the proxy classes should reside
on the BizTalk box but since the signature is same I am curious to know
how it works.
Appreciate your responses.
TIA,
Kiran Pabba
| |
| Tomas Restrepo \(MVP\) 2006-05-31, 1:16 pm |
| Pabba,
>
> I'm currently calling multiple web services running on a remote machine
> from my orchestration. Now that we have a new version of web service
> code running on a seperate remote box I'm adding this new web service
> references to my BizTalk project and pointing my ports to call this
> instead of old, resulting in rebuilding my code. The signature of this
> new web service version is same as the old one.
>
> My doubt is, in future everytime my web service location is going to
> change do I need to rebuild my code to reference this new web service
> thru add web references or could I make use of binding files by
> providing the url details for my SOAP adapter and just proceed. I do
> understand that to execute web service the proxy classes should reside
> on the BizTalk box but since the signature is same I am curious to know
> how it works.
If the WSDL for the services is exactly the same (i.e. if the interface of
both services is the same), then just reconfiguring the URL on the send port
(or creating an alternate send port and rebinding) would do the trick.
--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/
| |
|
| Thanks Tomas,
This should help since my interface is not going to change.
Regards,
Kiran Pabba
|
|
|
|
|