Set additional HTTP transport properties for JAX-RPC Web services with an assembly tool

This page explains how to configure additional HTTP transport properties for JAX-RPC Web services with an assembly tool. The assembly tool is used to configure the ibm-webservicesclient-bnd.xmi deployment descriptor binding file.

Configure additional HTTP transport properties with assembly tools provided with WAS.

This task is one of three ways that we can configure additional HTTP transport properties for a Web Service acting as a client to another Web service. We can also configure the additional HTTP transport properties in the following ways:

• Configuring additional HTTP transport properties using the JVM custom property panel in the admin console
• Configure the properties using the wsadmin command-line tool.

To programmatically configure the properties using the JAX-RPC model or the Java API for XML Web Services (JAX-WS) model, review the JAX-RPC or JAX-WS specifications.

For a complete list of the supported standards and specifications, see the Web services specifications and API documentation. For more information about the following HTTP properties that we can configure, read about HTTP custom properties for Web services applications:

• com.ibm.websphere.webservices.http.requestContentEncoding
• com.ibm.websphere.webservices.http.responseContentEncoding
• 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 - We 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.

Set the additional HTTP properties with an assembly tool with the following steps provided in this task section:

 

1. Start an assembly tool. Read about starting the assembly tool in the Rational Application Developer documentation.

2. If we have not done so already, configure the assembly tool so that it works on Java EE modules. we need to make sure that the Java EE and Web categories are enabled. Read about configuring the assembly tool in the Rational Application Developer documentation.

3. Migrate the WAR files that are created with the Assembly Toolkit, Application Assembly Tool (AAT) or a different tool to the Rational Application Developer assembly tool. To migrate files, import the WAR files to the assembly tool. Read about migrating code artifacts to an assembly tool in the Rational Application Developer documentation.

4. Set the additional HTTP transport properties. Create and specify the name/value pair in the Web Services Client Port Binding page for a Web service client. The Web Services Client Port Binding page is available after double-clicking the client deployment descriptor file. Read about configuring HTTP transport properties in the Rational Application Developer documentation.

 

Results

we have configured additional HTTP transport properties for a Web services application.

Assembly tools

 

Related tasks

Secure Web services applications at the transport level
Set additional HTTP transport properties using the JVM custom property panel in the admin console
Set additional HTTP transport properties using the wsadmin command-line tool
Set a Web services client to access resources using a Web proxy

 

Related

HTTP transport custom properties for Web services applications
Java virtual machine custom properties
Web services specifications and APIs