|
Problem(Abstract) |
After applying the Java™ 2 SDK update, the updateInstaller
logs indicate that the fix is properly applied to WebSphere® Application
Server. However, checking the WebSphere Application Server Java 2 SDK
version shows that no update was installed. |
|
|
|
Cause |
Some interim fixes deliver a Java 2 SDK update to the
WebSphere Application Server v5.0 product. Interim fix PQ81989 is an example of an interim fix which
delivers a Java 2 SDK update. This issue results in a "false
installation", which gives misleading indications that the Java 2 SDK was
successfully installed, when in reality no update was actually delivered.
There is a known issue concerning these type of interim fixes with
WebSphere Application Server v5.0 without fix packs installed. This issue
is present on v5.0.0, and also on higher fix levels delivered directly by
the product installer. For example, this issue is present on v5.0.2 for
Microsoft® Windows® 2003, which is delivered directly as v5.0.2 without
fix packs installed. This issue is also present for version v5.0.2 of the
WebSphere Test Environment (WTE) shipped with releases of WebSphere Studio
Application Developer v5.1.
During a false installation, the updateInstaller utility attempts
to install the interim fix. The installation operation completes nearly
instantaneously, and reports that the installation is successful. However,
an examination of the Java 2 SDK associated with the product shows that no
update was delivered. Additionally, a careful examination of the log files
show that there is a problem with the update.
A truly successful installation of an interim fix, which delivers an
updated Java 2 SDK, produces at least two log files in the
install_root/logs/update directory, both of which
report success messages. The datestamp and timestamp for these two logs
files are very similar. The files are names using the following convention
(using PQ81989 as an example of the interim fix ID):
datestamp_timestamp_PQ81989_OS_install.log
datestamp_timestamp_PQ81989_OS_prereq.jdk_install.log
A false installation of PQ81989 produces only the install.log file.
The prereq.jdk file is missing in that scenario. If a different
interim fix is applied, the log files use the PQ number of the interim
fix.
The root cause of this issue is a missing file from the directory,
install_root/properties/version. The
prereq.jdk.component file is not properly placed in that
directory during product installation. The updateInstaller depends on the
presence of this file to properly deliver the Java 2 SDK update. The
updateInstaller is instructed not to update the Java 2 SDK when this file
is not present. |
|
|
Resolving the
problem |
There are two possible ways to resolve this issue:
- Apply a fix pack
This issue is corrected in v5.0 Fix Pack 1, and all future fix packs for v5.0
include the fix. Apply a fix pack first, then apply any necessary
cumulative fixes. After the fix packs and cumulative fixes are applied,
the Java 2 SDK update can be applied successfully.
Neither v5.0 Fix Pack 1 nor v5.0 Fix Pack 2 should be applied to WebSphere
Application Server if it is already at v5.0.2. For example, do not apply
v5.0 Fix Pack 2 to the WebSphere Test Environment (WTE) delivered with
releases of WebSphere Studio Application Developer v5.1.
- Apply PQ82074
Alternatively, this issue can be resolved with interim fix PQ82074. Interim fix PQ82074 delivers the prereq.jdk.component file that
properly prepares the product to accept the Java 2 SDK update. First apply
interim fix PQ82074. Then in a new updateInstaller session, apply the
interim fix which delivers the Java 2 SDK update (for example: PQ81989).
Note: It is not necessary to apply PQ82074 if WebSphere Application Server v5.0 has been
updated using a fix pack.
After you apply one of the preceding fixes, verify that the update is
successful:
- Verify the update using logs
The installation of the interim fix is successful when the file,
datestamp_timestamp_PQXXXXX_win_prereq.jdk_install
appears in the update/logs directory. Check the bottom ten lines
of this file for a message similar to this:
End of extraction for
temp_dir\efixes\PQ99999_OS\components\prereq.jdk\update.jar
completed with no errors.
- Verify the update using the java -version command
Check the Java version using this procedure:
- For UNIX® platforms:
- From a command line, change to the directory
install_root/bin.
- Type the following command:
. ./setupCmdLine.sh
- Change directory to install_root/java/bin.
- Type the following command:
./java -version
- Verify that the Java version reported is the appropriate version for
the Java 2 SDK update. Refer to the Java 2 SDK update page to determine
which version the fix delivers. (For example, PQ81989 delivers 1.3.1 SR6 for AIX®, SR11 for Sun,
and SR13 for HP-UX.)
- For Windows® platforms:
- From a command line, change to the directory
install_root\bin.
- Type the following command:
setupCmdLine.bat
- Change directory to install_root\java\bin.
- Type the following command:
java -version
- Verify that the Java version reported is the appropriate version for
the Java 2 SDK update. Refer to the Java 2 SDK update page to determine
which version the fix delivers. (For example, PQ81989 delivers 1.3.1 SR6 for Windows.)
|
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Software Development |
WebSphere Studio Application Developer |
Install and migration |
Linux, Windows |
5.1 |
All Editions |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|