Prepare HP-UX systems for installation

This topic describes how to prepare an HP-UX system for the installation of IBM WebSphere Application Server, V6 products.

 

Before you begin

The installation uses a InstallShield for Multiplatforms (ISMP) wizard. We can use the graphical interface of the wizard. We 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.

 

Overview

Use the following procedure to prepare the operating system for the installation of WAS products.

 

Procedure

  1. Log on as root.

    We 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.

    In addition, 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

  2. Optional: Download and install the Mozilla Web browser so that use the launchpad application on the product disc. If you do not have the Mozilla Web browser, download and install the browser from http://www.mozilla.org.

  3. 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=/opt/bin/mozilla

  4. Stop all WebSphere Application Server-related Java processes on the machine where you are installing the product.

  5. Stop any Web server process such as the IBM HTTP Server.

  6. Provide adequate disk space.

    Attention:

    The Network Deployment product requires the following disk space:

    780 MB for the /opt/IBM/WebSphere/AppServer directory before creating profiles

    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:

    30 MB for the Deployment manager profile

    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.

    200 MB for an application server profile with the Sample applications

    This size does not include space for applications that you might develop and install.

    10 MB for an unfederated custom profile

    This size does not include space for applications that you might develop and install. The requirement does include space for the node agent. However, 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.

    100 MB for the /tmp directory

    The temporary directory is the working directory for the installation program.

    880 MB total requirement

    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:

    110 MB for the /opt/IBMIHS directory

    The IBM HTTP Server product requires this space.

    25 MB for the /opt/ibm/gsk7 directory

    The run-time module is gsk7bas for HP-UX platforms.

    The following space is the maximum amount that is required for the Web server plug-ins for WebSphere Application Server:

    280 MB for the /opt/IBM/WebSphere/plugins directory

    25 MB for the /opt/ibm/gsk7 directory

    The following space is required for the IBM WAS Clients:

    150 MB for the /opt/IBM/WebSphere/AppClient directory

    The amount of space required to install the application clients is actually less than 150 MB. The amount of space depends on the clients that you install as features.

    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.

    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 application objects:

    • For V4.0.x: The size of EAR files

    • For V5.0.x: The size of EAR files

  7. 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:

    1. Log into the host machine as root.

    2. Determine the physical memory, which know to avoid setting certain kernel parameters above the physical capacity:

      1. Start the HP-UX System Administration Manager (SAM) utility.

      2. Select Performance Monitors > System Properties > Memory.

      3. Note the value for Physical Memory and click OK.

      4. Exit from the SAM utility.

    3. 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:

      1. Open the /usr/conf/master.d/core-hpux file in a text editor.

      2. Change the line," *range maxfiles<=2048" to "*range maxfiles<=60000"

      3. Change the line, "*range maxfiles_lim<=2048" to "*range maxfiles_lim<=60000"

      4. 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:

        1. Move the existing version of the /var/sam/boot.config file to another location, such as the /tmp directory.

        2. Start the SAM utility.

        3. 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

    4. Set new kernel parameter values:

      1. Start the SAM utility.

      2. Click Kernel Configuration > Configurable Parameters.

      3. For each of the parameters in the following table, perform this procedure:

        1. Highlight the parameter to change.

        2. Click Actions > Modify Configurable Parameter.

        3. Type the new value in the Formula/Value field.

        4. Click OK.

      Change typical kernel settings for running WebSphere Application Server in the order shown in the following table:

      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 WAS 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.

    5. Click Actions > Process New Kernel.

    6. 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.

    7. If you plan to redirect displays to non-HP machines, do the following before running the WAS installation wizard:

      1. Issue the following command to obtain information on all the public locales that are accessible to your application 

        # locale -a

      2. 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.iso8859

  8. Verify that prerequisites and corequisites are at the required release levels.

    Although the Installation wizard checks for prerequisite operating system patches with the prereqChecker application, review the prerequisites on the IBM WAS 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.

  9. 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.

    1. Type which cp at the command prompt before running the installation program for the WAS product.

    2. 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.

    3. Install the WAS product.

    4. 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 install_root/java directory.

    Missing files can destroy required symbolic links. If you remove the freeware cp command from the PATH, install the Application Server product successfully.

    Perform the following step to verify that the Java 2 SDK is working correctly.

  10. Verify that the Java 2 SDK on your copy of the product CD is functioning 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.

    1. Change directories to the /mnt/JDK/repository/prereq.jdk/java/bin directory on the product CD-ROM. For example 

      cd /mnt/JDK/repository/prereq.jdk/java/bin

    2. Verify the Java 2 SDK version. Type the following command 

      ./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, install the WAS 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.