Skip to Content
0
Former Member
Oct 19, 2005 at 03:20 PM

Deployable web service proxies across dev/test/prod

57 Views

When you create a web service and deploy it across multiple environments (ie dev/test/prod) there is no configuration changes required, since the web service is installed and made accessible based on the installed server hostname. Great. However, how does this work for web service proxies?

When you generate a proxy, you point the wizard at a wsdl, and you get your proxy. However, this proxy points at the server which was referenced from the wsdl, which in a development environment may not be the eventual target server that exposes the web service (think of a development environment talking to a development web service, test talking to test, etc).

In NWDS, the configuration for the logical port for the proxy contains the 'target address' - how can one change this config item when the compiled object is installed across multiple (perhaps different) environments? I've perused the docs and the Visual Admin tool, but I can't find any information on this, other than this statement:

<i>After transport or re-deployment of the proxy, the URL and other important parameters can be adapted using a simple editor.</i>

Ok, great. Unfortunately the detail is slightly lacking in the above statement. Where does one edit these paramters?