This topic describes how to prepare a Linux system for installing WebSphere Application Server.
Before you begin
Why and when to perform this task
Steps for this task
If you do not have the Firefox browser, download and install the browser from http://www.mozilla.org/products/firefox/.
The run-time module is gskkm.rte.
The run-time module is gsk7bas.i386.rpm for Linux distributed platforms and gsk7bas.s390.rpm for Linux for S/390 platforms.
The addNode command script can fail when adding a node, or the importWasprofile command can fail when importing a configuration archive. The importWasprofile command might fail during the installation of a customized installation package (CIP) when the CIP includes a customized profile.
Set a higher ulimit setting for the kernel in the bash shell profile script, which is loaded at login time for the session.
See http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg2 1223909http://www.ibm.com/support/docview.wss?rs=180&context=SSEQTP&uid=swg2 1223909 for more information.
A Linux package registration limitation prevents the prerequisites checker program 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 Opteron, EM64T, iSeries, pSeries (PowerPC), and zSeries (S/390 64-bit) machines.
By default, RHEL 4 only installs 64-bit run-time support on these platforms. However, various applications included with WebSphere Application Server V6.x products and packages also require the 32-bit run-time support. Therefore, you must also install the 32-bit run-time support.
Install the following required 32-bit packages by selecting to customize the packages during the RHEL 4 installation. Or, customize packages on an existing RHEL 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 Application Server products and packages.
Install both the 32-bit version and the 64-bit version of the package on 64-bit z/Series 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.
After installing the V6.0 WebSphere Application Server product or package, install the latest refresh pack. The RHEL 4 operating system is supported beginning with V6.0.1 (Refresh Pack 1).
See Preparing RHEL 4 for the installation of WebSphere Application Server V6.0.1 and V6.0.2 products for more information.
A Linux package registration limitation prevents the prerequisites checker program from examining prerequisite packages on Linux systems. Verify that the following prerequisite packages are installed.
Required for C++ run-time compatibility. Used by such components as GSKit, the Java 2 Software Development Kit (SDK), and Web server plug-ins for WebSphere Application Server.
Required by some IBM HTTP Server modules. The modules use the libraries contained within this RPM package.
InstallShield for Multiplatforms (ISMP) requires the package to properly register products with the Red Hat Package Manager (RPM) database.
The following additional RPM packages are recommended for developing and building Java Native Interface (JNI) libraries for use by your Java 2 Enterprise Edition (J2EE™) applications. If you do not intend to compile JNI libraries on the system, you do not have to install the following packages:
iSeries platforms and pSeries platforms: Install the rpm-build-4.2.1-4.2 package. InstallShield for Multiplatforms (ISMP) requires the package to properly register products with the Red Hat Package Manager (RPM) database.
Required by some IBM HTTP Server modules. The modules use the libraries contained within this RPM package.
Required for C++ run-time compatibility. Used by such components as GSKit, the Java 2 Software Development Kit (SDK), and Web server plug-ins for WebSphere Application Server.
Required by InstallShield for Multiplatforms (ISMP) to properly register products with the Red Hat Package Manager (RPM) database.
You can install a later release of any of these packages.
Upgrade the RHEL 3 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 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.
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.
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.
SLES 9 does not require an additional service pack.
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 Application Server products to display garbled characters in the Simplified Chinese locale and in the Traditional Chinese locale.
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 on the Power PC machine and reboot the machine to solve the problem.
Result
What to do next
See Preparing to install Network Deployment on a Linux system for the next step in the overall procedure, which is selecting the type of installation to perform.
Related tasks
Preparing to install Network Deployment on a Linux system
Preparing the operating system for product installation