Network Deployment (Distributed operating systems), v8.0 > Reference > Sets
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.
For transitioning users: We must use HTTP transport channels instead of HTTP transports to handle your HTTP requests on all of your other nodes.trns
The use of IPv6 (IPv6) 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 admin console page...
Servers > Server Types > WebSphere application servers > server_name
> Web container settings > Web container > HTTP transports .
Host
Host IP address to bind for transport. If the application server is on a local machine, the host name might be localhost.
Port
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 that are allowed per process.
SSL Enabled
Whether to protect transport connections with SSL. The default is not to use SSL.
Configure transport chains
Related
HTTP transport settings