on 10-19-2005 4:20 PM
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?
Ken,
I think you are looking for server environment variables. I know when I was working with tomcat, I made the changes within server.xml and they differed from dev to test to prod, but the names were the same. This way within your code you can get the cotext lookup the variable and use it instead.
If this is what you are looking for, let me know. I need the same thing on SAP Netweaver and haven't got to it, but will be getting to it next.
Nathan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.