+

Search Tips   |   Advanced Search

Configure additional HTTP transport properties using wsadmin-line tool

We can configure additional HTTP transport properties for Java API for XML-based RPC (JAX-RPC) web services with wsadmin-line tool.

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

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:

To programmatically configure the properties using the Java API XML-based Remote Procedure Call (JAX-RPC) programming model or the JAX-WS programming model, review the JAX-RPC or JAX-WS specifications.

For more information about the following HTTP properties that we can configure, read about HTTP custom properties for web services applications:

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

  1. Launch a scripting command.

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

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

    Avoid trouble: This property is for JAX-RPC only, and it will not be used if it is enabled for services based on JAX-WS.gotcha

  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:

The following illustrates an example of the Jacl 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.


Related tasks

  • Configure additional HTTP transport properties for JAX-RPC web services with an assembly tool
  • Configure additional HTTP transport properties using the JVM custom property panel in the administrative console
  • Configure a web services client to access resources using a web proxy

  • Options for the AdminApp object install, installInteractive, edit, editInteractive, update, and updateInteractive commands
  • HTTP transport custom properties for web services applications
  • Web services specifications and APIs