|
Problem |
Enabling IBM® HTTP Server 2.0 plug-in support with
WebSphere® Application Server V4.0 releases prior to V4.0.5. |
|
Solution |
Statement of support
IBM HTTP Server 2.0 with the WebSphere Application Server plug-in is
fully tested and supported with V4.0.5 and all future WebSphere
Application Server V4 releases.
V4.0.2 through V4.0.4 supports use of IBM HTTP Server 2.0, after the
WebSphere Application Server cumulative plug-in fix, dated Dec 9, 2003 (or
later) is installed.
IBM recommends using IBM HTTP Server 2.0 rather than IBM HTTP Server 1.3
whenever possible. IBM also strongly recommends applying the latest
WebSphere Application Server cumulative plug-in fix.
Download:
IBM
HTTP Server 2.0.x
WebSphere Application Server cumulative plug-in fixes 4.0.x,
5.0.x,
5.1.x
With a support contract, IBM fully supports the following IBM HTTP
Server/plug-in combinations with WebSphere Application Server V4.0:
- IBM HTTP Server 2.0.42.x with V4.0 or V5.0
plug-in
- IBM HTTP Server 2.0.47.x with V5.1 plug-in
Prerequisites
- You must have a contract for all installed components if
your WebSphere Application Server version does not match the plug-in
version . For example, if you enabled WebSphere 5.0 plug-in with WebSphere
4.0 Application Server you must have a contract for both V4.0 and V5.0
versions.
Primary reasons for recommending IBM HTTP Server 2.0 as a Web server
for use with WebSphere Application Server V4.0 releases
1. IBM HTTP Server 2.0 is a thread-based Web Server
IBM HTTP Server 1.3 is thread-based on the Microsoft® Windows® platform.
It is process-based on all Unix® and Linux® platforms. IBM HTTP Server 2.0
has the advantage of being fully thread-based on all platforms.
Benefits of using a thread-based Web server:
- Each HTTP and HTTPS request does not require its own HTTPD
process, so significantly less memory is needed.
- Overall performance improves because in most cases new
HTTPD processes do not need to be created.
- The plug-in load-balancing algorithms work more
efficiently in a single-process, multithreaded HTTP server.
- You will see significantly fewer TCP/IP sockets in the
CLOSE_WAIT state on the remote Web server side.
2. IBM HTTP Server 2.0 includes mod_deflate module
The DEFLATE output filter, mod_deflate, compresses output from the
server before sending data to the client. Advantages of using mod_deflate
module:
- Saves network bandwidth during data transmission.
- Shortens data transmission time.
- Improves overall performance.
For details on how to use mod_deflate and some sample configurations,
refer to the following document that is available from the Apache Web
site:
http://httpd.apache.org/docs-2.0/mod/mod_deflate.html
3. New IBM HTTP Server 2.0 codebase
IBM HTTP Server 2.0 contains a new engine that is the platform for future
development. Significant improvements in technology should not be expected
in the IBM HTTP Server 1.3.x products.
Additional resources
Installing and configuring IBM HTTP Server 2.0
- IBM
HTTP Server library
Manually configuring the WebSphere Application Server HTTP plug-in for
use with IBM HTTP Server 2.0; refer to the following WebSphere Information
Center articles
- For releases of WebSphere Application Server v4.0 and
v5.0:
- Manually configuring supported Web servers
- plugin-cfg.xml elements and attributes
- For releases of WebSphere Application server v5.1:
- Manually configuring supported Web servers
- plugin-cfg.xml elements and attributes
Capturing MustGather information needed by IBM to troubleshoot
WebSphere Application Server HTTP plug-in issues with IBM HTTP Server
2.0
- MustGather:
WebSphere Application Server HTTP plug-in problems
|
|
|
|
|
|
|