The installation uses an InstallShield for Multiplatforms (ISMP)
wizard. You can also install the product silently. Silent mode is invoked
at a command line with a parameter that identifies an options response file,
which you edit before installing.
Use the following procedure to prepare the operating system for
installation of WebSphere Process Server.
- Log on as root.
You cannot install the product correctly
as a non-root user. If you create copies of the product CDs, do so as root.
Copies made by non-root users do not preserve the correct file attributes
and do not work.
- Verify that the umask setting is 022.
To verify
the umask setting, issue the following command:
umask
To set the umask setting to 022, issue the following command:
umask 022
- Optional: Install the Mozilla browser if it is not
already installed. The Mozilla browser supports the Launchpad console.
Download and install the Mozilla browser from http://www.mozilla.org.
- Optional: Export the location of the supported browser.
Export the location of the supported browser using a command that
identifies the actual location of the browser.

For
example, if the Mozilla package is in the
bin/mozilla directory,
use the following command:
export BROWSER=/usr/bin/mozilla

- Stop all Java processes on the machine on which you are installing
the product that are related to WebSphere Application Server, WebSphere Application
Server Network Deployment, or WebSphere Process Server.
- Stop any Web server process such as the IBM HTTP Server.
- Provide adequate disk space. See Required disk space for the space required to install WebSphere
Process Server and related products.
- Verify that prerequisites and corequisites are at the required
release levels.

Although the Installation Wizard
checks for prerequisite operating system patches, review the prerequisite
supported hardware and software for
WebSphere Process Server if
you have not already done so. To access this information, see WebSphere Process
Server detailed system requirements at
http://www.ibm.com/support/docview.wss?uid=swg27006205 and
select the link to your version of
WebSphere Process Server.

Refer
to the documentation for non-IBM prerequisite and corequisite products to
learn how to migrate to their supported versions.
- Provide necessary prerequisites for Red Hat Enterprise Linux V3.0.
A known limitation exists in the prerequisites checker program when
examining prerequisite packages on Linux systems.
You must install the
following packages on Red Hat Enterprise Linux V3.0 for xSeries platforms:
- compat-gcc-7.3-2.96.122
- compat-libstdc++-7.3-2.96.122
- compat-libstdc++-devel-7.3-2.96.122
- compat-glibc-7.x-2.2.4.32.5
- compat-gcc-c++-7.3-2.96.122
- compat-db-4.0.14-5
- rpm-build-4.2.1-4.2
The following package is required for Red Hat Enterprise Linux
V3.0 for pSeries platforms: rpm-build-4.2.1-4.2.
You can install a later
release of any of these packages.
- Upgrade Red Hat Enterprise Linux V3.0 to service level 4.
Upgrade the Red Hat Enterprise Linux V3.0 service level by downloading
and installing the service updates from Red Hat.
If you do not upgrade
the service level, certain national language issues in the released version
of GLIBC included in Red Hat Enterprise Linux V3.0 might cause Java Virtual
Machine (JVM) failures due to segmentation faults. These failures can occur
during installation when the locale is set to anything other than an English
locale.
Do not install, log off, and log back on when you are installing
from the operator console attached to the machine. This action can produce
segmentation faults that cause the installation to fail.
- Prepare the SuSE Linux Enterprise Server 8.0 - Powered by UnitedLinux
1.0 operating platform for WebSphere Process Server installation,
by performing the following steps:
- Install SP3 for the United Linux 1.0 operating platform to let
you use the Launchpad.
It is your responsibility to install
this service pack. The prereqChecker function of the installer cannot detect
service pack versions definitively on United Linux. Kernel unames and versions
between 8.0 and 8.0.3 are identical. No signature RPM denotes a service pack
install.
- Use the IBM Developer Kit that WebSphere Application Server
provides to support the Java 2 SDK on the SuSE SLES 8.0 operating system to
avoid potential problems when uninstalling an interim fix or a Fix Pack.
To use the IBM Developer Kit, remove the java2-jre-1.3.1-524 and
java2-1.3.1-524 RPMs from the machine before installing WebSphere Process
Server.
- Correct font problems on SuSE Linux Enterprise Server 8.0 in Simplified
Chinese and Traditional Chinese locales.
On the Linux for Power
platform that SuSE Linux Enterprise Server 8.0 provides, a missing package
causes a font problem. The ttf-hanyi package is not installed during
the normal product installation of the SuSE 8.0 operating system. The missing
package causes the Installation Wizard for WebSphere Process Server
to display garbled characters in the Simplified Chinese locale and in the
Traditional Chinese locale.
To fix this problem, copy the ttf-hanyi-2021016-0.noarch.rpm package
on the SuSE 8.0 for i386 CD to the Power PC system, install the package, and
reboot the machine.
- Verify that the system cp command is used, rather than the cp command
provided by emacs or other freeware.
If you install the product
using a cp command that is part of a freeware package, rather than
with the system cp command, the installation might appear to complete
successfully, but the Java 2 SDK that the product installs might have missing
files in the install_root/java directory (where install_root represents
the installation directory of WebSphere Process Server).
Missing
files can destroy required symbolic links. You must remove the freeware cp command
from the PATH in order to install the WebSphere Process Server product
successfully.
If you have emacs or other freeware installed on your
operating system, perform the following steps to identify which cp command
is being used by the system, and to deactivate the freeware cp command
if it is being used:
- Type which cp at the command prompt before running
the installation program for the WebSphere Process Server product.
- If the resulting directory output includes freeware,
remove the freeware directory from your PATH. For example,
if the output is similar to .../freeware/bin/cp, remove the
directory from the PATH.
- After you install WebSphere Process Server,
add the freeware directory back to the PATH.
- Verify that the Java 2 SDK on your copies of the product CDs is
functioning correctly.
If you created your own product CDs from
ISO images or by copying the actual CDs, perform the following steps to verify
that the Java 2 SDK is working correctly.
- On your created product CD for WebSphere Process Server CD
1, navigate to the /mnt/JDK/repository/prereq.jdk/java/bin directory. To do this, issue the following command:
cd /mnt/JDK/repository/prereq.jdk/java/bin
- Verify the Java 2 SDK version. To do this, issue
the following command:
./java -version
The command completes successfully with no
errors when the Java 2 SDK is intact.
- Repeat this procedure on your created product CD for WebSphere
Process Server CD 2.
After preparing the operating system, you can install WebSphere
Process Server. See Installing the product for
descriptions of the various installation alternatives available.