You can configure additional HTTP transport properties
with the JVM custom properties panel in the administrative console.
About this task
This task is one of three ways that you can configure additional
HTTP transport properties for a Web Service acting as a client to
another Web service. You can also configure the additional HTTP transport
properties in the following ways:
If
you want to programmatically configure the HTTP properties using the
Java API XML-based Remote Procedure Call (JAX-RPC) programming model,
review the JAX-RPC specification that is available through Web services:
Resources for learning.
For
more information about the following HTTP properties that you can
configure, read about HTTP custom properties for Web services applications:
- com.ibm.websphere.webservices.http.requestContentEncoding
- com.ibm.websphere.webservices.http.responseContentEncoding
Avoid trouble: ![[Updated in April 2012]](../../delta.gif)
This property is
for JAX-RPC only, and it will not be used if it is enabled for services
based on JAX-WS.
![[Updated in April 2012]](../../deltaend.gif)
apr2012
gotcha
- com.ibm.websphere.webservices.http.connectionKeepAlive
- com.ibm.websphere.webservices.http.requestResendEnabled
- com.ibm.websphere.webservices.http.SocketTimeout
- com.ibm.ws.webservices.enableHTTPPrefix
- http.proxyHost
- http.proxyPort
- https.proxyHost
- https.proxyPort
- http.nonProxyHosts - You can only configure this property as a
JVM custom property. This property applies for both HTTP and HTTPS
connections.
These additional properties are configured for Web services
applications that use the HTTP protocol. The properties affect the
content encoding of the message in the HTTP request, the HTTP response,
the HTTP connection persistence and the behavior of an HTTP request
that is resent after a java.net.ConnectException error occurs
when there is a read time-out.