HTTP transport collection

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: You can use HTTP transports only on a V5.1 node in a mixed cell environment. Use HTTP transport channels instead of HTTP transports to handle your HTTP requests on all of the other nodes.trns

The use of IPv6 (Internet Protocol V6) and WS-AT are not supported on HTTP transports; they are only supported on HTTP transport channel chains.

To view the HTTP Transport admin console page, click Servers > Server Types > WebSphere application servers > server_name > Web container settings > Web container > HTTP transports .

Host

Specifies the 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 appserver instance on a given machine.

For i5/OS 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.

---

 

Related tasks

Set transport chains

 

Related

HTTP transport settings