Getting Started with WebSphere Application Server

196 Getting Started with WebSphere Application Server Community Edition
11.2 Problems during installation/un-installation
The process of installing or uninstalling Community Edition is normally straight-forward;
however there may be situations as described in this section where you may encounter
problems.
11.2.1 JVM not found
The install or uninstall wizard needs a Java run time to be launched. It is strongly
recommended that the JAVA_HOME environment variable is set. Otherwise, you can specify
the Java run time (JVM) location by invoking the launcher from a command prompt or
terminal window with the LAX_VM wizard option where javaPath is the fully
qualified location of your Java executable file. For example,
wasce_setup-2.1.1.3-win.exe LAX_VM c:\java
tells the installer the JVM location is c:\java. For more information about the LAX_VM
option, review the online manuals at
http://publib.boulder.ibm.com/wasce/V2.1.1/en/setup-reference.html#Setupreferencecmdwiz
11.2.2 Platform-specific Problem
On different platforms, users may have different problems. Listed below are some common
problems in the Linux platform:
11.2.2.1 Linux dependent packages are missing
The GUI installation wizard has dependencies on legacy compatibility libraries
(libstdc++.so.5 and libXp.so.6) that must be installed on the target system. Some Linux
distributions have these packages installed by default, but not in others. Table 11.1 lists the
pre-requisite libraries required depending on the Linux distribution.
Platform
32-bit openSUSE 11
64-bit openSuSE 11
32-bit RHEL 5
32-bit Fedora 7 & 8
32-bit Asianux Server 3
64-bit RHEL 5,
64-bit Fedora and Fedora 8,
Prerequisite
libXp-1.0.0-8 and compat-libstdc++-33-3.2.3
32-bit or 64-bit libXp-1.0.0-8
32-bit or 64-bit compat-libstdc++-33-3.2.3
libXp-1.0.0-8
compat-libstdc++-33-3.2.3
32-bit or 64-bit libXp-1.0.0-8
32-bit or 64-bit compat-libstdc++-33-3.2.3