|
Problem(Abstract) |
A WebSphere® Application Server V5 fix pack or cumulative
fix fails during the webui component. The log shows errors such as "Failed
to find deployed EAR", "Error 59 - Copy Failed", "The system cannot find
the drive specified", and "The system cannot find the network path
specified". |
|
|
|
Cause |
Although some of these indicators might be due to various
known user errors or limitations, the inclusion of most, or all, indicate
incorrect data for WebSphere Application Server variables such as
WAS_HOME or JAVA_HOME. These variables are normally set
inside the <WAS_HOME>/bin/setupCmdLine script.
You can set a WAS_USER_SCRIPT environment variable to a
custom-made script which will override certain variables set inside
setupCmdLine. Consequently during normal Application Server
operations, the Application Server will invoke this user script and use
its data instead of that inside the setupCmdLine script which is
normally invoked.
However, during a fix pack or cumulative fix upgrade, the updateInstaller
ignores this WAS_USER_SCRIPT override and instead parses the
values set in the setupCmdLine script internally. The consequence is that
any variable overridden by WAS_USER_SCRIPT, such as
WAS_HOME, are not set to the expected value in the
WAS_USER_SCRIPT, causing various "file not found" and copy
failure errors.
If the WebSphere Application Server environment uses the
WAS_USER_SCRIPT in setupCmdLine, then the following
solution should resolve these issues. |
|
|
Resolving the
problem |
Ensure that the setupCmdLine.sh (or .bat on
Windows® systems) script is revised to include the information from
WAS_USER_SCRIPT before performing a fix pack or cumulative fix
upgrade. After the update is successful, the variables can be reset to
their previous values after the successful completion of the upgrade.
When editing setupCmdLine, make sure to replace existing
environment values, rather than append new values to the file. Only one
occurrence of each environment variable should appear in
setupCmdLine.sh.
Make sure to check the content of the setupCmdLine file in case
a fix pack uninstallation operation is performed. A fix pack
uninstallation can restore an earlier version of setupCmdLine,
which causes any revisions to the file to be lost. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|