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 a distributed platform,
HTTP transport support is deprecated. Therefore, the administrative console
page used to configure an HTTP transport is not available unless you migrated
an HTTP transport from your V5 environment. You must define an HTTP transport
channel instead of an HTTP transport to handle your HTTP requests.
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
- Change the configuration for an existing HTTP transport.
- Ensure that virtual host aliases include port values for the
transport your are changing.
- Go to the HTTP Transports page and click on the transport under Host whose
configuration you want to change.
Remember,
on a distributed platform, HTTP transport support is deprecated. Therefore
you cannot view this administrative console page unless you are a V5.x user
who, during the V6 migration process, indicated that you want to continue
using the HTTP transports that are defined for your V5 environment.
- On the settings page for an HTTP transport, which might have
the page title DefaultSSLSettings, change the specified values as needed,
then click OK.
- Custom properties page, add and set any HTTP transport custom
properties you want to use.
- 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.
If
the Web server is defined on an unmanaged node and is not an IBM HTTP Server
V6.0 Web server, copy the updated plugin-cfg.xml file
to the remote Web server and replace the file that is there.
If the Web server is an IBM HTTP Server V6.0
Web server, is located on a machine remote from the Application Server, and
is defined on an unmanaged node, you can configure the plugin-cfg.xml file
so that whenever it is updated, it is automatically propagated to the remote
IBM HTTP Server.