|
Problem(Abstract) |
This document describes how to recover from
updateInstaller failures in unusual situations where the IBM® WebSphere®
Application Server V5.0, V5.1, and V6.0 updateInstaller is unable to
properly clone the Java™ SDK for its own use. |
|
Cause |
If the updateInstaller utility for WebSphere Application
Server V5.0, V5.1, or V6.0 does not properly clone the Java SDK, it may be
necessary to manually clone it. Note that the updateInstaller should
correctly clone the updateInstaller as long as the best practices for
initialing the updateInstaller are followed. However, in the isolated
cases where the updateInstaller is unable to successfully clone the Java
SDK, this procedure can be used to work around the issue.
Note for WebSphere Application Server V6.0
IBM WebSphere Application Server support recommends using the V6.1
updateInstaller utility to update WebSphere Application Server V6.0
products. The latest version of the V6.1 updateInstaller is compatible
with the WebSphere Application Server V6.0 product.
The V6.1 updateInstaller does NOT require Java SDK clones. The V6.1
updateInstaller is packaged with its own Java SDK, and therefore does not
need to clone it from the application server. Using the V6.1
updateInstaller instead of the V6.0 updateInstaller will resolve issues
related to the Java SDK cloning process. |
|
Resolving the
problem |
Before resorting to this procedure,review the following
points:
- Best practices for initializing the V5.0 and V5.1
updateInstaller recommends that the updateInstaller be placed in a
directory named "update" or "updateinstaller" within the product's main
directory. (For example, "/opt/WebSphere/AppServer/update".)
- The V6.0 updateInstaller requires that the
updateInstaller be placed in a directory named "updateinstaller" within
the product's main directory. (For example,
"/opt/WebSphere/AppServer/updateinstaller".) If the V6.0 updateInstaller
is not placed within the product's main directory, it will not start up
and my throw errors indicating that it could not find "a suitable JVM."
For details on how to accomplish this, refer to technote 1205400
. If that technote corrects issues related to the location of the
updateInstaller, then the procedure in this technote is likely
unnecessary.
Note: The V6.1 updateInstaller does not have this requirement. It
can be installed to any reasonable location on the system.
- The updateInstaller utility for V5.0, V5.1, and V6.0 must
be run as the root user on UNIX®- and Linux®-based systems, not as
a non-root user and not as "sudo root". This is documented in the product
Information Center and in technote 1168943
. Failure to run the updateInstaller as the root user can potentially
interfere with the Java SDK cloning process. If switching to the root user
and running the updateInstaller corrects an issue, then the procedure in
this technote is likely unnecessary.
- The updateInstaller utility is sensitive to the use of
"setupCmdLine". Failure to source setupCmdLine before the first use of an
updateInstaller instance can interfere with the Java SDK cloning process.
The cloning process will not take place again until the situation is
corrected. Refer to technote 1168526
for V5.0 and V5.1, or refer to technote 1214653
for V6.0, to correct this situation. Following those other procedures
usually corrects Java SDK cloning issues, which means the procedure in
this technote is unnecessary in those cases.
After reviewing the points mentioned above, refer to the instructions
for the appropriate version of WebSphere Application Server:
Manually cloning the Java
SDK for updateInstaller V6.0:
- Ensure that the updateInstaller is extracted to the proper
location. The updateInstaller must be executed from a directory named
"updateinstaller", and that directory must be located within the product's
main directory. For example, the updateInstaller should be in the
directory, "/opt/IBM/WebSphere/AppServer/updateinstaller". For extensive
details, refer to technote 1205400
.
- Copy the "java/jre" directory from the targeted product into the
"updateinstaller" directory. (For IBM HTTP Server V6 installations,
the "java" directory may not exist. See the directions below for further
details.)
For Windows®-based systems, copying is a straightforward copy operation.
(Select the "jre" folder inside the targeted product's "java" folder in
Windows Explorer and use the "Copy" function. Then, "Paste" that folder
into the "updateinstaller" directory.)
For UNIX- or Linux-based systems, the "cp" command is sufficient to copy
the "jre" directory. However, it is important to preserve symbolic links
during the copy operation using the "-Rpfd" parameters. Use the command as
illustrated in this example:
cd install_root/updateinstaller
cp -Rpfd ../java/jre .
In this example, install_root represents the installation directory
of the target product.
For IBM HTTP Server installations, the "java" directory may not exist in
the targeted product. In that case, use the "_jvm/jre" directory in place
of the "java/jre" directory mentioned above.
- Once the "jre" directory is copied into the updateinstaller
directory, rename it to "java".
For Windows-based systems, this is a straightforward rename operation.
(Select the "jre" folder inside the "updateinstaller" folder and use File
-> Rename.)
For UNIX- or Linux-based systems, the "mv" command is sufficient to
accomplish this. For example:
cd install_root/updateinstaller
mv jre java
- Attempt to run the updateInstaller again. The updateInstaller
should automatically locate the Java SDK located in the "update/java"
directory and run smoothly. Use a sequence of commands similar to the
following to ensure that setupCmdLine is properly sourced before launching
the updateInstaller:
Windows-based systems
cd install_root\bin
setupCmdLine.bat
cd ..\updateinstaller
update.exe
UNIX- or Linux-based systems
cd install_root/bin
. ./setupCmdLine.sh
cd ../updateinstaller
./update
Note: The "dot-space" preceding the "dot-slash setupCmdLine.sh" is
very important. The "dot-space" performs the "source" operation. Be sure
to type the command exactly as shown.
Manually cloning the Java
SDK for updateInstaller V5.0 or V5.1:
- Ensure that the updateInstaller is extracted to the recommended
location. The updateInstaller should be executed from a directory
named "update", and that directory should be located within the product's
main directory. For example, the updateInstaller should be in the
directory, "/opt/WebSphere/AppServer/update".
- Copy the "java" directory from the targeted product into the
"update" directory.
For Windows-based systems, copying is a straightforward copy operation.
(Select the "java" folder inside the targeted product in Windows Explorer
and use the "Copy" function. Then, "Paste" that folder into the
"updateinstaller" directory.)
For UNIX- or Linux-based systems, the "cp" command is sufficient to copy
the "java" directory. However, it is important to preserve symbolic links
during the copy operation using the "-Rpfd" parameters. Use the command as
illustrated in this example:
cd install_root/update
cp -Rpfd ../java .
In this example, install_root represents the installation directory
of the target product.
- Once the "java" directory is copied into the updateinstaller
directory, rename it to "java_tmp".
For Windows-based systems, this is a straightforward rename operation.
(Select the "java" folder inside the "update" folder and use File ->
Rename.)
For UNIX- or Linux-based systems, the "mv" command is sufficient to
accomplish this. For example:
cd install_root/update
mv java java_tmp
- Attempt to run the updateInstaller again. The updateInstaller
should automatically locate the Java SDK located in the "update/java_tmp"
directory and run smoothly.
Windows-based systems
cd install_root\bin
setupCmdLine.bat
cd ..\update
updatewizard.bat
UNIX- or Linux-based systems
cd install_root/bin
. ./setupCmdLine.sh
cd ../update
./updateWizard.sh
Note: The "dot-space" preceding the "dot-slash setupCmdLine.sh" is
very important. The "dot-space" performs the "source" operation. Be sure
to type the command exactly as shown.
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|
|