|
Problem(Abstract) |
The updateInstaller is used to apply Fix Packs to the
WebSphere Application Client, including the "pluggable" client. However,
the updateInstaller fails to start up when attempting to install on the
pluggable client, stating that the "core.dll" file is missing. |
|
|
|
Cause |
When attempting to install a Fix Pack or other maintenance
on a WebSphere Application Client V5 installed as a "pluggable client",
the updateInstaller utility fails to start. The updateInstaller will
report the following error:
Can't load library "CLIENT_HOME\java\jre\bin\core.dll", because Can't
find dependent libraries.
Could not create the Java virtual machine.
For nearly all the editions and installation scenarios of WebSphere
Application Server and WebSphere Application Client, a copy of the IBM
Java™ SDK is included in the java subdirectory of that
installation. The updateInstaller requires the IBM Java SDK as a
prerequisite. As a result, the updateInstaller was designed to take
advantage of the IBM Java SDK included with that installation.
When the updateInstaller utility is invoked, it will first make a
temporary copy of the content of the
Install_Root \java subdirectory.
(Install_Root refers to The WAS_HOME value as defined in
setupCmdLine.bat, which you are required to invoke before starting the
updateInstaller). The updateInstaller then invokes that temporary copy of
java, using that copy as its runtime environment. The updateInstaller
cannot actually use the files in the java subdirectory since it may
deliver fixes to those same files. Therefore, it is necessary to make this
temporary copy of java.
By design, the pluggable client installation uses some conventions which
are different than a standard application server and application client
installation. The pluggable client installation only includes a small set
of files in its java directory. These files do not comprise a full
IBM Java SDK, and are not sufficient for running the updateInstaller. When
the updateInstaller is invoked in a pluggable client environment, it
attempts to use this partial set of IBM Java SDK files. This causes
problems, and the updateInstaller throws errors indicating that it is
unable to start up due to missing files. In most scenarios, the error
indicates that core.dll is missing, but there is a much larger set
of files required by the updateInstaller that are not present.
|
|
|
Resolving the
problem |
In order to resolve this problem, it is necessary to
redirect the updateInstaller to use a full copy of the IBM Java SDK. In a
standard WebSphere Application Client pluggable client installation
scenario, an IBM Java SDK is already present in the installation. The
following procedure describes a solution to this issue:
- Open a command prompt and navigate to the CLIENT_HOME\bin directory.
- Run setupCmdLine.bat. (This will set several environment variables,
including WAS_HOME and JAVA_HOME.)
- Manually redefine JAVA_HOME variable to the %WAS_HOME%\_uninst\_jvm
directory. In order to do so, run this command:
set JAVA_HOME=%WAS_HOME%\_uninst\_jvm
%WAS_HOME% represents the full path to the WebSphere Application Client
installation.
Ensure that the value of JAVA_HOME represents the full path to the _jvm
subdirectory of the WebSphere Application Client installation using this
command:
echo %JAVA_HOME%
If the %WAS_HOME%\_uninst\_jvm directory does not exist or does not
contain a working copy of an IBM Java SDK, then it is necessary to obtain
an IBM Java SDK from an external source. An IBM Java SDK can be obtained
from the WebSphere Application Client product installation CD in the
"jdk\java" subdirectory. Once an IBM Java SDK is obtained, copy it to a
temporary directory (NOT %WAS_HOME%\java) and change the JAVA_HOME
environment variable to refer to that directory.
- Run the updateInstaller again. This time, the updateInstaller should
be able to make a temporary copy of that IBM Java SDK and start up without
error. Follow the normal Fix Pack installation procedure to apply the Fix
Pack to the WebSphere Application Client product.
- Once the installation is complete, run setupCmdLine.bat (see steps 1
and 2) to ensure JAVA_HOME is set back to the proper value.
As a result of following this procedure, the updateInstaller should be
able to start up and operate on the WebSphere Application Client pluggable
client installation. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|