Configuring HTTP transports

To define the characteristics of the connections between that plug-in and the Web container, you must configure the request queue (the HTTP transport) between a WebSphere Application Server plug-in for a Web server, and a Web container in which the Web modules of an application reside.

About this task

Important: On the z/OS platform, the administrative console page used to configure an HTTP transport will always be available. The HTTP transport that is created by the WebSphere Application Server for z/OS ISPF Customization Dialog is a required element of the WebSphere Application Server for z/OS runtime. Optionally, you can configure an HTTPS transport using the HTTP Transport panel of the administrative console, or new Version 6 HTTP transport channels using the Channel/Chain Configuration panel.

The use of IPv6 (Internet Protocol Version 6) and WS-AT (Web Services Atomic Transactions) are not supported on HTTP transports; they are only supported on HTTP transport channel chains.

An HTTP transport is the request queue between a WebSphere Application Server plug-in for Web servers and a Web container in which the Web modules of an application reside. To define the characteristics of the connections between that plug-in and the Web container, you must specify:

Important: Only one HTTP transport and one HTTPS transport can be defined per Application Server.

Procedure

  1. Change the configuration for an existing HTTP transport.
    1. Ensure that virtual host aliases include port values for the transport your are changing.
    2. Go to the HTTP Transports page and click on the transport under Host whose configuration you want to change.
    3. On the settings page for an HTTP transport, which might have the page title DefaultSSLSettings, change the specified values as needed, then click OK.
    4. Custom properties page, add and set any HTTP transport custom properties you want to use.
  2. Stop the WebSphere Application Server and start it again. You must stop the WebSphere Application Server and start it again before the configuration changes you made take affect.

What to do next

If the Web server is located on a machine remote from the Application Server but is defined on a managed node, the updated plugin-cfg.xml is automatically propagated to the Web server.




In this information ...


Related concepts
Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=trun_plugin_transport
File name: trun_plugin_transport.html