HTTP transport collection
Use this page to view or manage HTTP transports. Transports provide request queues between web server plug-ins 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.
(zos) transition: Use HTTP transports only on a V6.0.x node in a mixed cell environment. We must use HTTP transport channels instead of HTTP transports to handle the HTTP requests on all of the other nodes.
transition: We must use HTTP transport channels instead of HTTP transports to handle your HTTP requests on all of the other nodes.
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 console page, click Servers > Server Types > WebSphere application servers > server_name > Web container settings > Web container > HTTP transports.
Host IP address to bind for transport. If the application server is on a local machine, the host name might be localhost.
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 IBM i and distributed operating systems, there is no limit to the number of HTTP ports allowed per process.
(zos) For z/OS , 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.
Whether to protect transport connections with SSL. The default is not to use SSL.
HTTP transport settings