The installation of WebSphere Application Server
Enterprise Edition V5.0 for Network Deployment fails on Linux platforms.
The WAS.PME.install.log file shows a NullPointerException for the
updateParentSoftwareObject method. Here is a partial listing of the stack
trace:
com.installshield.product.service.product.PureJavaProductServiceImpl
$Installer, err, java.lang.NullPointerException STACK_TRACE: 17
java.lang.NullPointerException
at
com.installshield.product.service.registry.PureJavaRegistryServiceIm
pl.updateParentSoftwareObject(PureJavaRegistryServiceImpl.java:573)
at
java.lang.reflect.Method.invoke(Native Method)
at
com.installshield.wizard.service.LocalImplementorProxy.invoke
(LocalImplementorProxy.java(Compiled Code))
at
com.installshield.wizard.service.AbstractService.invokeImpl
(AbstractService.java(Compiled Code))
at
com.installshield.product.service.registry.GenericRegistryService.up
dateParentSoftwareObject(GenericRegistryService.java:216)
at
com.installshield.product.service.product.PureJavaProductServiceImpl
$InstallProduct.updateParentOnChildren
(PureJavaProductServiceImpl.java:4811)
at
com.installshield.product.service.product.PureJavaProductServiceImpl
$InstallProduct.addToVPD(PureJavaProductServiceImpl.java:4670)
at
[truncated for brevity]
This might occur when the based edition of WebSphere Application Server
is installed first, then Enterprise Edition is installed on top of it.
WebSphere Application Server Network Deployment is installed next, on the
same physical system. After that, Enterprise Edition is installed on top
of the existing Network Deployment installation, which results in a
failure. |
This specific failure is a known issue, documented in the
Release Notes for Enterprise Edition in the section "Installation of IBM
WebSphere Application Server Enterprise, Version 5 might fail on SuSE
Linux and Red Hat® Linux". See that article for full details about this
issue.
The following is one possible solution to this issue.
Note: This excerpt is from the article in the Release Notes.
Additional solutions are provided in the Release Notes; however, this
solution is the least disruptive of the solutions presented in the
article. (See the additional note below this section for details on
the ramifications of this solution).
- Run the following rpm commands in a shell prompt:
rpm -q WSEOS07AA-5.0-0 WSESA07AA-5.0-0 WSEFC06AA-5.0-0
WSEEM05AA-5.0-0 WSECF11AA-5.0-0
- This command displays whether or not the entries exist. It is possible
that they do not exist on your system and the installation process will
work without them. If the entries exist, the previous command produces the
following output:
WSEOS07AA-5.0-0
WSESA07AA-5.0-0
WSEFC06AA-5.0-0
WSEEM05AA-5.0-0
WSECF11AA-5.0-0
- If the entries exist, type the following to erase them from the
rpm command:
rpm -e WSEOS07AA-5.0-0 WSESA07AA-5.0-0 WSEFC06AA-5.0-0
WSEEM05AA-5.0-0 WSECF11AA-5.0-0
- If the following error appears after issuing the preceding command,
ignore it. The error displays if one of the entries is not in the rpm.
error: package WSEFC06AA-5.0-0 is not installed
- Run the following command to confirm that the entries are erased:
rpm -q WSEOS07AA-5.0-0 WSESA07AA-5.0-0 WSEFC06AA-5.0-0
WSEEM05AA-5.0-0 WSECF11AA-5.0-0
- If the entries are erased, the following messages display:
package WSEOS07AA-5.0-0 is not installed
package WSESA07AA-5.0-0 is not installed
package WSEFC06AA-5.0-0 is not installed
package WSEEM05AA-5.0-0 is not installed
package WSECF11AA-5.0-0 is not installed
- Install IBM WebSphere Application Server Enterprise on IBM WebSphere
Application Server Network Deployment.
Note: This solution can affect the Enterprise Edition
uninstaller for the Enterprise Edition product installed with the based
WebSphere Application Server product. In the future, after uninstalling
the Enterprise Edition product, we recommend that you use the manual
uninstall instructions for WebSphere Application Server V6.0 on Linux,
located in the Information Center, to clean up the operating system.
|