Configuring additional HTTP transport properties using the wsadmin command-line tool

This topic explains how to configure additional HTTP transport properties with the wsadmin command-line tool.

 

Before you begin

The WAS wsadmin tool provides the ability to run scripts. Use the wsadmin tool to manage a WebSphere Application Server installation, as well as configuration, application deployment, and server run-time operations. The WAS only supports the Jacl and Jython scripting languages. For more information about the wsadmin tool options, review Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands

 

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 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.

See Additional HTTP transport properties for Web services applications for more information about the following properties that you can configure:

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 the wsadmin tool by following steps provided in this task section:

 

Procedure

  1. Launch a scripting command.

  2. At the wsadmin command prompt, enter the command syntax. Use install, installInteractive, edit, editInteractive, update, and updateInteractive commands.

  3. If you are configuring the com.ibm.websphere.webservices.http.responseContentEncoding property, use the WebServicesServerCustomProperty command option.

  4. Configure all other properties using the WebServicesClientCustomProperty command option.

  5. Save the configuration changes with the $AdminConfig save command.

 

Results

You have configured HTTP transport properties for a Web services application.

 

Example

The following illustrates an example of the Jython script syntax

AdminApp.edit ( 'PlantsByWebSphere', '[ -WebServicesClientCustomProperty [[PlantsByWebSphere.war "" 
service/FrontGate_SEIService FrontGate http.proxyHost+http.proxyPort myhost+80]]]') 
AdminConfig.save()  

AdminApp.edit ( 'WebServicesSamples', '[ -WebServicesServerCustomProperty 
[[AddressBookW2JE.jarAddressBookService AddressBook http.proxyHost+http.proxyPort myhost+80]]]') 
AdminConfig.save()  


The following illustrates an example of the Jacly script syntax

$AdminApp edit PlantsByWebSphere {  -WebServicesClientCustomProperty {{PlantsByWebSphere.war {}
service/FrontGate_SEIService FrontGate  http.proxyHost+http.proxyPort myhost+80 }}} 
$AdminConfig save

$AdminApp edit WebServicesSamples {-WebServicesServerCustomProperty {{AddressBookW2JE.jar 
AddressBookService AddressBook http.proxyHost+http.proxyPort myhost+80}}} 
$AdminConfig save
To convert these examples from edit to install, add .ear to form a file name, and add any extra keywords for deployment, like -usedefaultbindings and -deployejb.

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.