Follow this procedure to prepare a Linux system for installation of WebSphere Process Server.
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 a response file, which you edit before installing.
Use the following procedure to prepare the operating system for installation of WebSphere Process Server.
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.
umask
umask 022
Export the location of the supported browser using a command that identifies the actual location of the browser.
export BROWSER=/opt/bin/firefox
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.
A Linux package registration limitation prevents the prereqChecker program in the installer from examining prerequisite packages on Linux systems. Verify that the following prerequisite packages are installed. See Installing and verifying Linux packages for more information.
Installing packages for all hardware platforms
Install the following packages on any hardware platform:
These packages are part of the Red Hat Enterprise Linux 4 operating system, but are not installed by default. You can also install a later release of any of these packages if Red Hat provides new packages as errata.
Selecting packages for hardware platforms that are capable of running both 32-bit and 64-bit applications
Hardware platforms capable of running both 32-bit and 64-bit applications include AMD Opteron, Intel(R) EM64T, iSeries, pSeries (PowerPC(R)), and zSeries (S/390 64-bit) machines.
By default, Red Hat Enterprise Linux 4 only installs 64-bit runtime support on these platforms. However, various applications included with WebSphere Process Server products and packages also require the 32-bit runtime support. Therefore, you must also install the 32-bit runtime support.
Install the following required 32-bit packages by selecting to customize the packages during the Red Hat Enterprise Linux 4 installation. Or, customize packages on an existing Red Hat Enterprise Linux 4 system by issuing the system-config-packages command from a graphical terminal.
Install the Compatibility Architecture Support under the System category. Optionally install the Compatibility Architecture Development Support under the Development category if you intend to build C or C++ libraries for use with both 32-bit and 64-bit applications.
Run the rpm -qa | grep package_name command to verify that you have both versions of each package. Substitute the name of each package for the package_name variable.
Installed packages are displayed in the reply to the command. If you do not get two replies for each package, you have only one version of the package installed. You must then install the missing package.
Installing additional packages for specific platforms
In addition to the packages that are common to all platforms, install the following packages on hardware platforms capable of running both 32-bit and 64-bit applications, before installing WebSphere Process Server products and packages.
Install both the 32-bit version and the 64-bit version of the package on 64-bit zSeries hardware platforms.
Problems encountered when you do not install required packages
If you do not install all of the required packages, the Installation wizard cannot start. Error messages indicate missing libraries, the inability to load graphical interfaces, or other errors that occur during the installation.
SLES 9 SP1 is the officially supported platform for PowerPC 64-bit machines.
00000014 RecoveryManag A WTRN0028I: Transaction service recovering 0 transactions. 0000000a ResourceMgrIm I WSVR0049I: Binding DefaultTimerManager as tm/default 0000000a WorkAreaServi A ACWA0002I: WorkArea service not enabled on dmgr. 0000000a AppProfileCom I ACIN0007I: The application profiling service started successfully. 0000000a CacheServiceI I DYNA0048I: WebSphere Dynamic Cache initialized successfully. 00000015 LogAdapter E DCSV9416E: An internal error occurred. Exception is Clock not changed in 10002 rounds. 00000015 LogAdapter E DCSV9416E: An internal error occurred. Exception is Clock not changed in 10002 rounds.
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:
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.
cd /mnt/JDK/repository/prereq.jdk/java/bin
./java -versionThe command completes successfully with no errors when the Java 2 SDK is intact.
This procedure prepares the operating system for installation of WebSphere Process Server.
After preparing the operating system, you can install WebSphere Process Server. See Installing the software for descriptions of the various installation alternatives available.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)