Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 18, 2012 10:08 PM by janilane
Nov 16, 2012 01:02 AM|LINK
Im trying to troubleshoot a web client that calls a WCF service that resides in the same web server, and this web service is then trying to connect to the database by calling another service that resides in another server. It is interesting to note that
their client endpoint address are:
1. Web client - endpoint address points to the same service in the same server using Http binding;
2. Web service 1 - this service that resides in the same web server as the web clients has the endpoint address pointing to the second web service that resides in a different server where it has the connection to the database.
My understanding is that a web service should expose the endpoint address OF ITSELF, so any client can find it and connect using that URL, binding and contract. So why is then the first web service has its address pointing to the second web service that
resides in a different server? Is this a valid endpoint?
Nov 16, 2012 01:48 PM|LINK
Your client application should have a <client> configuration that points to service1.
Service1 should have a <service> setting which defines the endpoint information, so that clients can talk to it.
Service1 should also have a <client> configuration which points to service2 because this is what it allows it to talk to other services.
Service2 has its own <service> settings, so it can be found by clients.
Service1 should have something like this:
<endpoint address="http://service2-here" />
<endpoint address="http://service1-here" binding="wsHttpBinding"
Nov 18, 2012 10:08 PM|LINK
Thanks for this info, it takes away the confusion.