HTTP transport collection

 

+

Search Tips   |   Advanced Search

 

To manage HTTP transports, from the console, click...

Servers | Application Servers | server | Web Container Settings | Web Container | HTTP Transports

Transports provide request queues between WAS 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.

You can use HTTP transports only on a V5.1 node in a mixed WebSphere Application Server environment. You must use HTTP transport channels instead of HTTP transports to handle your HTTP requests on all of your other nodes.

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

Host

Specify 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 platforms, there is no limit to the number of HTTP ports that are allowed per process.

SSL Enabled

Specify whether to protect connections between the WebSphere plug-in and appserver with SSL. The default is not to use SSL.




 

Related tasks


Configure transport chains

 

Related Reference


HTTP transport settings

 

Reference topic