Choose a Proxy for One WebSphere 8.5.5 JAX-WS Client

For WebSphere Application Server 8.5.5 JAX-WS, check two surrounding controls before relying on a client request-context address. IBM's JVM-level com.ibm.ws.websvcs.transport.enableProxyTunnel defaults to false; a per-client address does not enable tunneling. A policy set's HTTP transport values also override programmatic values, which override JVM system properties.

For the selected existing port, IBM documents this per-client setup before invocation:

import javax.xml.ws.BindingProvider;

BindingProvider binding = (BindingProvider) servicePort;
binding.getRequestContext().put("https.proxyHost", "proxy.example");
binding.getRequestContext().put("https.proxyPort", "8080");

The HTTPS keys apply to HTTPS endpoints; use the corresponding IBM HTTP keys for HTTP. An allowed public SOAP endpoint can use an HTTP address from the HTTP proxy list only after the applicable policy and tunneling controls permit it and no proxy account is configured at those levels. Proxy authentication has separate HTTP/HTTPS proxyUser and proxyPassword properties, independent from SOAP service credentials.

These are WebSphere extensions. A BindingProvider map in Metro, CXF or another implementation does not make those strings portable.

Keep different concurrent routes on appropriately configured client objects instead of rewriting a shared port context while calls run. This scopes the address to the actual client without treating all of its surrounding JVM controls as client-local.