HTTP transport collection

 

+

Search Tips   |   Advanced Search

 

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

Servers | Application Servers | servername | 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.

On a distributed platform, if, when migrating from WAS V5.x, you indicate that you want to continue using an HTTP transport to handle your HTTP requests, your V5.x transports are migrated for you. If you are not migrating from V5.x, set up an HTTP transport channel to handle your HTTP requests.

Note that the use of IPv6 and WS-AT not supported on HTTP transports; they are only supported on HTTP transport channel chains.

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

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.

SSL Enabled

Specifies whether to protect connections between the WebSphere plug-in and application server with SSL. The default is not to use SSL.


 

See Also


Transports

 

Related Tasks


Configuring HTTP transports

 



 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.