|
Problem(Abstract) |
IBM WebSphere Application Server Fix Packs come with
updates to the IBM HTTP Server. In some instances, this can down level
code that is installed on your server. |
|
|
|
Cause |
WebSphere Application Server Fix Packs come with an update
for the IBM HTTP Server. The version of the update is the same as the
version that would install with the WebSphere Application Server
installation program. If you have installed a version other than the one
that comes as part of the WebSphere installation program, you might
corrupt your IBM HTTP Server installation.
This has become particularly evident with the advent of WebSphere
Application Server V5.0 and V5.1 releases where you are greatly increasing
your use of IBM HTTP Server V2.0 releases. However, it is also a problem
where any version of the IBM HTTP Server is used that is outside of the
normal installation of WebSphere, as would using the 1.3.28 version with
WebSphere Application Server V4.0 where it is shipped with 1.3.19. The
readme for the Fix Packs does mention that the Fix Pack is only for an
installation of the IBM HTTP Server that was installed with the WebSphere
installation. |
|
|
Resolving the
problem |
The solution is to use the IBM HTTP Server Support page as
a resource for updating your current version of the IBM HTTP Server when a
version has been installed that did not come with your WebSphere
Application Server installation. The IBM HTTP Server is installed as a
full installation and can be found from the Downloads section on
the main IBM
HTTP Server Support page.
IBM HTTP Server and plug-in only installation
In the case of a remote Web server plug-in only installation with the IBM
HTTP Server, you can still install the WebSphere Application Server Fix
Packs. In this scenario, you would choose to update the application
server. The Fix Pack installation code knows to only update the plug-in
components and then you could also specify the updating of your IBM HTTP
Server since it was installed as part of the WebSphere installation.
Updated functionality in the V5.1.1.3 Update Installer
Starting with the Update Installer for WebSphere Application Server
V5.1.1 Cumulative Fix 3 (5.1.1.3), the capability for the Update Installer
to review the directory where you specify to update the IBM HTTP Server
has been added. Below is the panel showing a user specifying an IBM HTTP
Server V2.0 installation for the 5.1.1.0 Fix Pack.
If a version is found other than the one that is installed with the
WebSphere installer, the following dialog box is displayed:
How does this apply to the installation of Fix Pack 1 (5.1.1) if the
functionality did not exist before Cumulative Fix 3 (5.1.1.3)?
Every fix, Fix Pack and Cumulative for V5.1, that is downloaded from the
IBM Support pages has an associated link for the Update Installer
download. Starting with releases of V5.0, the installation of fixes,
Cumulative Fixes and Fix Packs is done with the most current version of
the Update Installer. To download, see the V5.1
Update Installer page.
For your convenience, the latest copy of the Update Installer that was
available when a cumulative or Fix Pack is released is included in the
Cumulative or Fix Pack download. The functionality to check for the
version of the IBM HTTP Server became available in the version of the
Update Installer that was distributed in Cumulative Fix 3 (5.1.1.3).
Instructions on all cumulative, Fix Packs and fixes specify that the
latest Update Installer should be used to apply the fix. This allows IBM
to fix defects found in the Update Installer as they are encountered. So
defects found at the 5.1.1.0 level might apply even if you are applying
5.1.0.1, but if you download the latest Update Installer, you would not
encounter them.
This practice of downloading the latest Update Installer only started at
the V5.0 level and is not applicable for older versions of the WebSphere
Application Server. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|