Use this page to view or manage HTTP transports. Transports provide request queues between WebSphere Application Server 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.
If, when migrating from WebSphere Application Server Version 5.x, you indicate that you want to continue using an HTTP transport to handle your HTTP requests, your Version 5.x transports are migrated for you. If you are not migrating from Version 5.x, set up an HTTP transport channel to handle your HTTP requests.
To view the HTTP Transport administrative console page, click Servers > Application Servers > server_name > Web Container Settings > Web Container > HTTP Transports .
the HTTP Transport panel on the administrative console
The host IP address to bind for transport. If the application server is on a local machine, the host name might be localhost.
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.
Whether to protect connections between the WebSphere plug-in and application server with Secure Sockets Layer (SSL). The default is not to use SSL.
Related concepts
Transports
Related tasks
Configuring HTTP transports
Related reference
Administrative console preference settings
Administrative console page features
HTTP transport settings