Before you begin
The installation uses Installation Manager. You can
use the graphical interface or use a response file in silent mode.
Restriction: There are known issues with using Cygwin/X to run
Eclipse-based applications on remote HP-UX machines. This affects
your use of the Profile Management Tool. With Cygwin/X on remote HP-UX,
for example, the Profile Management Tool's welcome panel appears but
no keyboard or mouse input is accepted. For details of existing Bugzilla
reports on these issues, see the information at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=97808.
If a different X server (such as Hummingbird Exceed
®) is
used, these problems do not occur.
About this task
Preparing the operating
system involves such changes as allocating disk space and installing
patches to the operating system. IBM tests WebSphere Application Server
products on each operating system platform. Such tests verify whether
an operating system change is required for WebSphere Application Server products to
run correctly. Without the required changes, WebSphere Application Server products do
not run correctly.
- Log on to the operating system.
You
can log on as root or as a nonroot installer.
Select a umask
that allows the owner to read/write to the files, and allows others
to access them according to the prevailing system policy. For root,
a umask of 022 is recommended. For nonroot users a umask of 002 or
022 can be used, depending on whether the users share the group. To
verify the umask setting, issue the following command:
umask
To set the umask
setting to 022, issue the following command:
umask 022
- Optional: Download and install the Mozilla
Firefox web browser.
If you do not have the Mozilla
web browser, download and install the browser from Web Browsers for HP-UX.
- 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.
If the Mozilla Firefox package is in the
/opt/bin/firefox directory,
for example, use the following command:
export BROWSER=/opt/bin/firefox
- Stop all Java processes
related to WebSphere Application
Server on the machine where you are installing the product.
- Stop any web server process such as the IBM HTTP Server.
- Provide adequate disk space.
The amount
of
disk space required varies with the number of features or products
installed. If you are installing the product using Installation Manager,
the installation summary panel indicates the approximate amount of
disk space required based on the features and products you have selected.
Installing
all features and products requires approximately 2 GB of disk space.
This estimate includes the following products, components, and features:- Main application server product installation
- Profiles
- Sample applications
- IBM HTTP Server
- Web Server
Plug-ins
- Application Client for WebSphere Application Server
If you plan to migrate applications and the configuration
from a previous version, verify that the application objects have
enough disk space. As a rough guideline, plan for space equal to 110
percent of the size of the applications.
- Set kernel values to support Application Server.
Several
HP-UX kernel values are typically too small for the product.
To
set kernel parameters, perform the following steps:
- Log into the host machine as root.
- Determine the physical
memory, which you must know to avoid setting
certain kernel parameters above the physical capacity:
- Start the HP-UX System Administration Manager (SAM) utility with
the /usr/sbin/sam command.
- Select Performance
Monitors > System Properties >
Memory.
- Note the value for Physical Memory and
click OK.
- Exit from the SAM utility.
- Set the maxfiles and maxfiles_lim parameters to at least 4096.
The following table recommends 8000 and 8196, respectively. You must
first edit the /usr/conf/master.d/core-hpux file,
so the SAM utility can set values greater than 2048:
- Open the /usr/conf/master.d/core-hpux file
in a text editor.
- Change the line," *range maxfiles<=2048"
to "*range maxfiles<=60000"
- Change the line, "*range maxfiles_lim<=2048" to "*range
maxfiles_lim<=60000"
- Save and close the file. Old values might be stored in
the /var/sam/boot.config file.
Force the SAM utility to create a new boot.config file:
- Move the existing version of the /var/sam/boot.config file
to another location, such as the /tmp directory.
- Start the SAM utility.
- Select Kernel Configuration >
Configurable Parameters.
When the Kernel Configuration window opens, a new boot.config file
exists.
Alternatively, rebuild the
boot.config file
with the following command:
# /usr/sam/lbin/getkinfo -b
- Set new kernel parameter values:
- Start the SAM utility.
- Click Kernel Configuration >
Configurable Parameters.
- For each of the parameters in the following table, perform
this
procedure:
- Highlight the parameter to change.
- Click Actions > Modify Configurable Parameter.
- Type the new value in the Formula/Value field.
- Click OK.
Table 1. Typical kernel
settings for running WebSphere Application Server. Change typical kernel settings for running WebSphere Application
Server in the order shown in the following table:
Parameter
|
Value |
swchunk |
8192 |
shmmni |
8192 (Change this one before shmseg) |
shmseg |
512 |
maxdsiz |
3221225472 |
maxdsiz_64bit |
64424509440 |
maxfiles_lim |
10000 (Change this one before maxfiles) |
maxfiles |
8192 |
semume |
512 |
semmsl |
3072 |
msgssz (removed
and replaced by msgmbs in HP-UX
11.31) |
512 (Change this one before msgmax) |
nkthread |
10000 |
max_thread_proc |
4096 |
nproc |
8192 (Change this
one before maxuprc) |
maxuprc |
4096 |
ninode |
8110 |
msgtql |
13107 (Change this one before msgmap) |
msgseg (removed and replaced by msgmbs
in HP-UX
11.31) |
32767 (Change this one before
msgmap and msgmax) |
msgmap
(removed in HP-UX 11.31) |
13109 |
msgmnb |
65535
(0x10000) (Change this one before msgmax) |
msgmnb |
131070 (when running
multiple profiles on the
same system) |
msgmax
(removed in HP-UX 11.31) |
65535
(0x10000) |
msgmax
(removed in HP-UX 11.31) |
131070
(when running multiple profiles
on the same system) |
msgmbs
(added and replaced msgssz and msgseg
in HP-UX 11.31) |
8 |
msgmni |
4634 |
semmns |
11586 |
semmni |
8192 |
semmnu |
8180 |
shmmax |
185513715302 |
STRMSGSZ |
65535 |
dbc_max_pct |
10 |
nstrpty |
60 |
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.
- Click Actions > Process New Kernel.
- Click Yes on the information window to
confirm your decision to restart the machine.
Follow the on-screen
instructions to restart your machine and to enable the new settings.
- If you plan to redirect displays to non-HP machines, do the following
before installing:
- Issue the following command
to obtain information on all the public
locales that are accessible to your application:
# locale -a
- Choose a value for your system from the output that is displayed
and set the LANG environment variable to this value. Here is an example
command that sets the value of LANG to en_US.iso88591
# export LANG=en_US.iso88591
- Verify that prerequisites
and corequisites are at the required
release levels.
Although Installation Manager checks
for prerequisite operating system patches, review the prerequisites
on the Supported hardware and software website if
you have not done so already. Refer to the documentation for non-IBM
prerequisite and corequisite products to learn how to migrate to their
supported versions.
- Verify the system cp command
when using emacs or other freeware.
If you have emacs
or other freeware installed on your operating system, verify that
the system
cp command is used.
- Type the following command prompt before running the installation
program for the WebSphere Application
Server product.
which cp
- Remove the freeware directory from your PATH
if the resulting directory output includes freeware.
For example, assume that the output is similar to the following message: .../freeware/bin/cp.
If so, remove the directory from the PATH.
- Install the WebSphere Application
Server product.
- Add the freeware directory back to the PATH.
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 app_server_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.
- Verify that the Java SDK on the installation image disk is functioning
correctly if you created your own disk.
For example,
you might have downloaded an installation image from Passport Advantage®, or you might
have copied an installation image onto a backup disk. In either case,
perform the following steps to verify that the disk contains a valid Java software development kit (SDK).
- Change directories to the /JDK/jre.pak/repository/package.java.jre/java/jre/bin directory
on the product disk. For example:
cd /JDK/jre.pak/repository/package.java.jre/java/jre/bin
- Verify the Java version.
Type the following command:
./java -version
The
command completes successfully with no errors when the SDK is intact.