|
Problem |
Problems arise when there are multiple xerces.jar files in
the operating system path. This can cause unforeseen problems with fix
pack and interim fix updates. |
|
Cause |
If the wrong xerces.jar file is used during a WebSphere®
Application Server product update, XML files are not parsed correctly,
causing installation failure. |
|
Solution |
WebSphere Application Server uses the xerces.jar file to
parse XML. This is a key component of the installation process for
updating your Application Server since the xerces.jar determines the
manner in which an Interim fix, fix pack, or cumulative fix is installed.
There are instructions embedded in the fix JAR that are dependent upon the
xerces.jar file.
If a particular application needs to use a different version of the
xerces.jar, the application server for that application should configure
the classpath so that the xerces.jar can be loaded for that server only.
This keeps the non-WebSphere xerces.jar out of the WebSphere path and
independent of the application server. Files directly within the WebSphere
binary path should never be modified.
Troubleshooting xerces problems
On Windows® systems
On Windows systems, there are often multiple xerces files available in the
system path. If you are running a WebSphere update in a command prompt in
Windows, you have the option of typing:
SET PATH=
This deletes the system path. After that, the setupCmdLine.bat file
should be run in the same command window so that the JAVA_HOME and
WAS_HOME variables are set and found by the fix pack or interim fix
installation.
On UNIX® systems
On UNIX, you do not have the option of deleting the path because it is
integral in the operation of the operating system. You must take the
locations within your system path and locate non-WebSphere xerces.jar
files. When found, either move the xerces.jar out of the path or remove
that directory from the path statement. This keeps the WebSphere Update
Installer from using the incorrect xerces.jar file.
General best practices
Always run the setupCmdLine.bat (Windows) or setupCmdLine.sh
(UNIX) before installing WebSphere Application Server updates and fixes.
This is very important on systems with multiple Java™ software developer
kits installed. The Update Installer uses the xerces.jar to create the
uninstall jars for later use. If a version of Java is used that creates a
manifest.inf in a format that is unsupported, that installation can become
entirely corrupt and require reinstallation.
Always download the latest update installer for your version of WebSphere
Application Server v5.0 or v5.1 release. This helps in eliminating
problems that have been previously fixed by updates to the installation
program.
v5.0 UpdateInstaller
v5.1 UpdateInstaller
v6.0
UpdateInstaller
|
|
|
|
|
|
|