Network Deployment (Distributed operating systems), v8.0 > End-to-end paths > Web services - Transports > Use HTTP to transport web services


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

We can configure additional HTTP transport properties for JAX-RPC web services with the wsadmin command-line tool.

The WAS wsadmin tool provides the ability to run scripts. We can use the wsadmin tool 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 you 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:

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


Procedure

  1. Launch a scripting command.
  2. At the wsadmin command prompt, enter the command syntax. We can use install, installInteractive, edit, editInteractive, update, and updateInteractive commands.

  3. If you are configuring the com.ibm.websphere.webservices.//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/ .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 //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyHost+//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyPort myhost+80]]]')
AdminConfig.save()

AdminApp.edit ( 'WebServicesSamples', '[ -WebServicesServerCustomProperty
[[AddressBookW2JE.jarAddressBookService AddressBook //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyHost+//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyPort myhost+80]]]')
AdminConfig.save()
The following illustrates an example of the Jacl script syntax: 
$AdminApp edit PlantsByWebSphere {  -WebServicesClientCustomProperty {{PlantsByWebSphere.war {}
service/FrontGate_SEIService FrontGate  //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyHost+//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyPort myhost+80 }}}
$AdminConfig save
$AdminApp edit WebServicesSamples {-WebServicesServerCustomProperty {{AddressBookW2JE.jar
AddressBookService AddressBook //publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .proxyHost+//publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=/  .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.
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


Related


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

+

Search Tips   |   Advanced Search