Use this page to view or manage HTTP transports. Transports provide request queues between WebSphere Application Server plug-ins for Web servers and Web containers in which the Web modules of applications reside. When you request an application in a Web browser, the request is passed to the Web server, then along the transport to the Web container.
On a distributed platform,
if, when migrating from Version 5.x, you indicate that you want to continue
using an HTTP transport to handle your HTTP requests, your Version 5 transports
are migrated for you. If you are not migrating from WebSphere Application
Server Version 5.x, you must set up an HTTP transport channel to handle your
HTTP requests.
On the z/OS platform, the HTTP transport
is the default transport functionality for handling HTTP requests. The WebSphere
Application Server for z/OS ISPF Customization Dialog will continue to be
used to configure a default HTTP transport and, at most, one additional transport
for HTTPS. If you are a WebSphere Application Server for z/OS Version 5.x
user who has migrated to Version 6, note that the Version 5.x HTTP (and, optionally
HTTPS) transport definitions will remain unchanged in Version 6. You can use
the HTTP Transport page in the administrative console to configure these transports.
In Version 6, you can define additional HTTP listeners as HTTP transport channels.
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.
To view the HTTP Transport administrative console page, click Servers > Application Servers > server_name > Web Container Settings > Web Container > HTTP Transports.
Specifies the host IP address to bind for transport. If the application server is on a local machine, the host name might be localhost.
Specifies the port to bind for transport. The port number can be any port that currently is not in use on the system. The port number must be unique for each application server instance on a given machine.
For distributed platforms,
there is no limit to the number of HTTP ports that are allowed per process.
For the z/OS platform, a maximum of two ports, one for HTTP
requests and one for HTTPS requests, is allowed for each process configured
as an HTTP transport. Additional ports can be configured as HTTP transport
chains Additional ports can be configured as HTTP transport channels.
Specifies whether to protect connections between the WebSphere plug-in and application server with Secure Sockets Layer (SSL). The default is not to use SSL.