The embedded HTTP transport

 

Before moving on to the main part of this chapter, it is important to mention that WAS V5 has a built-in HTTP server, which we refer to as the embedded HTTP transport. It allows for direct connection from the user's browser to the application without the need for a separate Web server using the internal HTTP transport port. The HTTP service runs using the transport settings specified in the Web container setup, such as port 9080. You can find or

Manipulate these settings in the Administrative Console by selecting...

Servers | Application Servers | <AppServer Name> | Web Container | HTTP Transports.

Using the internal transport in the Web container is useful within development environments because there is no need to configure a separate Web server or to update the plug-in when changes are made to the URL mappings.

However, it is strongly recommended that this internal Web server not be used in production environments. If the user connects directly to the embedded HTTP transport, then they bypass the plug-in and the workload management it performs, as well as the failover and session affinity mechanisms. Refer to 6.1.1, "Using the embedded HTTP transport vs. a stand-alone Web server" of the redbook IBM WebSphere Version 5.0 System Management and Configuration, SG24-6195 for more details about this.

  Prev | Home | Next

 

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.