This document is provided for users that require support for IBM HTTP Server 7.0 and IBM web server Plug-in 7.0 as a front-end for IBM WebSphere Application Server 8.0 or 8.5.
For example, if you are using third-party modules in IBM HTTP Server 7.0 which have not yet been certified for use with IBM HTTP Server 8.0 or 8.5.
IBM HTTP Server 7.0 and IBM web server Plug-in 7.0 used with IBM WebSphere Application Server 8.0 or 8.5
Resolving the problem
Using the combination of IBM HTTP Server 7.0 and IBM web server Plug-in 7.0 in deployments with IBM WebSphere Application Server 8.0 and 8.5 is now recognized as a supported configuration by IBM. This toleration is provided as a transitional measure to allow users with third-party modules in IBM HTTP Server 7.0, which may not yet be certified by their authors for use in IBM HTTP Server 8.0 and later, to use IBM WebSphere Application Server 8.0 and 8.5.
This configuration will remain supported while IBM WebSphere Application Server 7.0 is in standard support.
Customers can check for updates to the End of Support date for WebSphere products at the following url:
IBM Software support lifecycle
As soon as possible, it is recommended to upgrade IBM HTTP Server and IBM web server Plug-in to match the same version as IBM WebSphere Application Server.
This documentation does not apply to IBM HTTP Server 8.0 and web server Plug-in 8.0 and higher. Refer to the following documentation on the plug-in policy for supported configurations.
Web server plug-in policy for WebSphere Application Server
- The Plugin Configuration Tool from V8R0 and later is not used in this environment.
- Web server definitions should be manually created in the IBM WebSphere Application Server administrative console.
- If new Plugin configuration directives are added in V8R0 and later, they may be reported as unrecognized when the Plug-in configuration is loaded. These messages can be minimized by using a 7.0 cumulative fix with a build date greater than or equal to the build date used to generate the configuration (typically the deployment manager). You can determine build dates of any component by executing bin/VersionInfo.sh(.bat) from a command prompt.