This topic describes how to prepare an HP-UX system for the installation of IBM WebSphere Application Server, Version 6 products.
Before you begin
The installation uses a InstallShield for Multiplatforms (ISMP) wizard. You can use the graphical interface of the wizard. You can also use the wizard in silent mode.
Silent mode is a command line invocation with a parameter that identifies an options response file. Edit the options response file before installing.
If you encounter a problem such as needing more temporary space or missing prerequisite packages on your operating system, cancel the installation, make the required changes, and restart the installation.
Why and when to perform this task
Use the following procedure to prepare the operating system for the installation of WebSphere Application Server products.
Steps for this task
You cannot install the product correctly as a non-root user.
If you create a copy of the product CD-ROM, do so as root. Copies made from 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/mozilla
The Network Deployment product requires the following disk space:
The installation root directory includes the core product files. This size does not include space for profiles or applications. Profiles require 40 MB of temp space in addition to the sizes shown. Profiles have the following space requirements:
This size does not include space for Sample applications that you might install. The size also does not include space for applications that you might deploy.
This size does not include space for applications that you might develop and install.
This size does not include space for applications that you might develop and install. The requirement does include space for the node agent. However, you must federate a custom profile to create an operational managed node.
After federating a custom profile, the resulting managed node contains a functional node agent only. Use the deployment manager to create server processes on the managed node.
The temporary directory is the working directory for the installation program.
This amount is the total space requirement when installing the product from the CD and when not installing service. Installing profiles requires more space.
The following space is required for the IBM HTTP Server product:
The following space is the maximum amount that is required for the Web server plug-ins for WebSphere Application Server:
The Installation wizard for each component displays required space on the confirmation panel before you install the product files and selected features. The Installation wizard also warns you if you do not have enough space to install the product.
# /usr/sam/lbin/getkinfo -b
Parameter | Value |
---|---|
STRMSGSZ | 65535 |
dbc_max_pct | 25 |
maxdsiz | 805306358 (0x30000000) |
maxdsiz | 2048000000 (when running multiple profiles on the same system) |
maxfiles_lim | 8196 (Change this one before maxfiles.) |
maxfiles | 8000 |
maxssiz | 8388608 |
maxswapchunks | 8192 |
max_thread_proc | 3000 |
nproc | 4116 (Change this one before maxuprc) |
maxuprc | 512 |
maxusers | 512 |
msgtql | 2046 |
msgmap | 2048 |
msgssz | 32 (Change this one before msgmax) |
msgseg | 32767 (Change this one before msgmax) |
msgmnb | 65535 (0x10000) (Change this one before msgmax) |
msgmnb | 131070 (when running multiple profiles on the same system) |
msgmax | 65535 (0x10000) |
msgmax | 131070 (when running multiple profiles on the same system) |
msgmni | 50 |
nfile | 58145 |
nflocks | 3000 |
ninode | 60000 |
nkthread | 7219 |
npty | 2024 |
nstrpty | 1024 |
nstrtel | 60 |
sema | 1 |
semaem | 16384 (0x4000) |
semmns | 16384 (0x4000) (Change this one before semmap) |
semmni | 2048 (Change this one before semmap) |
semmap | 514 |
semmnu | 1024 |
semume | 200 |
semvmx | 32767 |
shmem | 1 |
shmmax | 2147483647 (0x7FFFFFFF) |
shmmni | 1024 |
shmseg | 1024 |
When WebSphere Application Server and IBM DB2 are on the same machine, some kernel values are higher than those shown in the preceding table.
See the Recommended HP-UX kernel configuration parameters for DB2 V8 Web page for more information.
Follow the on-screen instructions to restart your machine and to enable the new settings.
# locale -a
# export LANG=en_US.iso8859
Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WebSphere Application Server supported hardware, software, and APIs Web site if you have not already done so.
Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.
If you install with a cp command that is part of a freeware package, 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.
Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, you can install the Application Server product successfully.
Perform the following step to verify that the Java 2 SDK is working correctly.
If you created your own product CD from an ISO image or by copying the actual CD, perform the following steps to verify that the Java 2 SDK on the product CD-ROM is working correctly.
cd /mnt/JDK/repository/prereq.jdk/java/bin
./java -version
The command completes successfully with no errors when the Java 2 SDK is intact.
Result
This procedure results in preparing the operating system for installing the product.
What to do next
After preparing the operating system for installation, you can install the WebSphere Application Server product.
See Preparing to install Network Deployment on an HP-UX system for the next step in the overall procedure, which is selecting the type of installation to perform.