Transports

 

+

Search Tips   |   Advanced Search

 

A transport is the request queue between a WebSphere Application Server plug-in for Web servers and a Web container in which the Web modules of an application reside. When a user at a Web browser requests an application, the request is passed to the Web server, then along the transport to the Web container.

Transports define the characteristics of the connections between a Web server and an application server, across which requests for applications are routed. Specifically, they define the connection between the Web server plug-in and the Web container of the application server.

Administering transports is closely related to administering WAS plug-ins for Web servers. Indeed, without a plug-in configuration, a transport configuration is of little use.

On a distributed platform, 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 (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.

 

The internal transport

The internal HTTP transport allows HTTP requests to be routed to the application server directly through a Web server plug-in. Logging is provided for debug purposes.

Prior to WAS V5.0.2, the HTTP transport functionality existed only as a means of accepting HTTP requests forwarded by an HTTP plug-in that was connected to a Web server. In WAS V5.0.2, HTTP transport functionality is now a supported internal Web server. By default, the internal HTTP transport listens for HTTP requests on port 9080 and for HTTPS requests on port 9443.

For example, use the URL...

http://localhost:9080/snoop

...to send requests to the snoop servlet on the local machine over HTTP and...

https://localhost:9443/snoop

...to send requests to the snoop servlet on the local machine over HTTPS.

The transport configuration is a part of the Web container configuration. One can configure the internal transport to use ports other than 9080 and 9443. However, also adjust your virtual host alias and what you type into the Web browser.


 

Related Tasks


Configuring access logging for internal Web server HTTP transport
Configuring error logging for internal Web server HTTP transport

 



 

 

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.