HTTP transport collection
Use this page to view or manage HTTP transports. Transports provide
request queues between WebSphere 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.
To view this administrative console page, click Servers > Application
Servers > server_name > Web Container > HTTP Transports.
- Host
- Specifies the host IP address to bind for transport. You may specify
* (asterisk) or an IP address, but IP names are not allowed.
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 WebSphere
Application Server for z/OS, a maximum of two http ports are allowed for each
process.
- SSL Enabled
- Specifies whether to protect connections between the WebSphere
Web server plug-in and an application server with Secure Sockets Layer (SSL).
When a client browser issues a non-SSL HTTP call to a Web server, the Web
server plug-in uses a non-SSL enabled port. When a client browser issues
an SSL HTTP call to a Web server, the Web server plug-in uses an SSL enabled
port.

Transports

Configuring transports

Administrative console buttons
Administrative console filter settings
Administrative console preference settings
Administrative console page features
HTTP transport settings
Searchable topic ID:
urun_rhttptransport
Last updated: Jun 21, 2007 4:55:42 PM CDT
WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/urun_rhttptransport.html