|
Problem(Abstract) |
This document describes how to recover from a failed
product maintenance update resulting from using an incorrect version of
the Java™ SDK with the UpdateInstaller for IBM® WebSphere® Application
Server versions 5.0 or 5.1. |
|
|
|
Cause |
If the environment is not properly initialized using the
setupCmdLine command, the UpdateInstaller fails. One of the most
common problems occurs when the update installer runs with the wrong Java
SDK.
The most common problems related to using the wrong Java SDK are
documented in other technotes. In the majority of cases, these scenarios
are corrected using the instructions below.
For more details regarding Fix Pack installation errors for Application
Server versions 5.0 or 5.1, refer to technote 1170359.
Please note that the details described in this technote apply
only to Application Server versions 5.0 and 5.1. For a description
of a similar solution appropriate for Application Server V6.0, please
refer to technote 1214653.
This solution is no longer necessary for Application Server V6.1, as the
UpdateInstaller for that product does not require special handling of the
Java SDK. |
|
|
Resolving the
problem |
Naming convention for "install_root"
Please note that in the instructions below, install_root
refers to the Application Server's main product directory. For example, on
UNIX®- or Linux®-based systems, this might be "/opt/WebSphere/AppServer",
or on Windows®-based systems, this might be "C:\Program
Files\WebSphere\AppServer".
UNIX® systems
- Make a backup of the "java_tmp" directory, located under the
UpdateInstaller's main directory. Then, delete the "java_tmp" directory.
Note: The Update Installer main directory can be located in a
directory of your choice. WebSphere support recommends that the Update
Installer be placed in install_root /update; for example,
/opt/WebSphere/AppServer/update .
This backup step is a precautionary step. It is good practice to preserve
the "java_tmp" directory in case other copies of "java" are missing or
corrupt. If the UpdateInstaller fails to start after following this
procedure, it is still possible to restore the "java_tmp" backup and use
the UpdateInstaller again.
- Change to the install_root /bin directory, and issue the
following command:
. ./setupCmdLine.sh
Note: The command begins with dot, space, dot, slash. The first
dot and space are very important and must be present for the command to
work properly.
- Verify that the WAS_HOME and JAVA_HOME environment variables are set
properly:
echo $WAS_HOME
echo $JAVA_HOME
Ensure that those commands return values that are correct for the
WebSphere Application Server installation directory. (For example,
"WAS_HOME" would be set to a directory such as
"/opt/WebSphere/AppServer".) The JAVA_HOME value should be very similar to
the WAS_HOME value, with "/java" appearing at the end of the value.
- Run the UpdateInstaller utility again. It recreates the "java_tmp"
directory that was deleted in Step 1, and it copies the correct Java SDK
into that directory.
Windows® systems
- Make a backup of the "java_tmp" directory, located under the
UpdateInstaller's main directory. Then, delete the "java_tmp" directory.
Note: The Update Installer main directory can be located in a
directory of your choice. WebSphere® support recommends that the Update
Installer be placed in <install_root>\update; for example,
C:\Program Files\WebSphere\AppServer\update .
This backup step is a precautionary step. It is good practice to preserve
the "java_tmp" directory in case other copies of "java" are missing or
corrupt. If the UpdateInstaller fails to start after following this
procedure, it is still possible to restore the "java_tmp" backup and use
the UpdateInstaller again.
- Open a command prompt session. Change to the <install_root
>\bin directory, and issue this command:
setupCmdLine.bat
- Verify that the WAS_HOME and JAVA_HOME environment variables are set
properly:
echo %WAS_HOME%
echo %JAVA_HOME%
Ensure that those commands return values that point at the WebSphere
Application Server installation directory. (For example, "WAS_HOME" would
be set to a directory such as "C:\Program Files\WebSphere\AppServer".) The
JAVA_HOME value should be very similar to the WAS_HOME value, with "\java"
appearing at the end of the value.
- Run the UpdateInstaller utility again from within the same command
prompt session. (Do not simply double-click "updatewizard.bat" from within
Windows File Explorer!) It recreates the java_tmp directory that was
deleted in Step 1, and it copies the correct Java SDK into that
directory.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|