Configuring additional HTTP transport properties for JAX-RPC web services with an assembly tool
You can configure additional HTTP transport properties for Java™ API for XML-based RPC (JAX-RPC) web services with an assembly tool. The assembly tool is used to configure the ibm-webservicesclient-bnd.xmi deployment descriptor binding file.
Before you begin
About this task
- Configuring additional HTTP transport properties using the JVM custom property panel in the administrative console
- Configure the properties using the wsadmin command-line tool.
If you want to programmatically configure the properties using the Java API XML-based Remote Procedure Call (JAX-RPC) programming model or the Java API for XML Web Services (JAX-WS) programming model, review the JAX-RPC or JAX-WS specifications.
지원되는 표준 및 스펙의 전체 목록은 웹 서비스 스펙과 API 문서를 참조하십시오.
- com.ibm.websphere.webservices.http.requestContentEncoding
- com.ibm.websphere.webservices.http.responseContentEncoding Note: 이 특성은 JAX-RPC 전용이며, JAX-WS 기반 서비스에 대해 사용으로 설정된 경우 이 특성은 사용되지 않습니다.
- 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.
Configure the additional HTTP properties with an assembly tool with the following steps provided in this task section:
Procedure
- Start an assembly tool. Read about starting the assembly tool in the Rational® Application Developer documentation.
- If you have not done so already, configure the assembly tool so that it works on Java EE modules. You 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.
- Migrate the web application archive (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 your WAR files to the assembly tool. Read about migrating code artifacts to an assembly tool in the Rational Application Developer documentation.
- Configure 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.