WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Preparing HP-UX systems for installation

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

Before you begin

Why and when to perform this task

Steps for this task

  1. Provide adequate disk space.
    Attention:
    780 MB for the /opt/IBM/WebSphere/AppServer directory before creating profiles
    30 MB for the Deployment manager profile
    200 MB for an application server profile with the Sample applications
    10 MB for an unfederated custom profile
    100 MB for the /tmp directory
    880 MB total requirement
    110 MB for the /opt/IBMIHS directory
    25 MB for the /opt/ibm/gsk7 directory

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

    280 MB for the /opt/IBM/WebSphere/plugins directory
    25 MB for the /opt/ibm/gsk7 directory
  2. 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 you must know to avoid setting certain kernel parameters above the physical capacity:
      1. Start the HP-UX System Administration Manager (SAM) utility with the /usr/sbin/sam command.
      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
      maxusers 512
      nkthread 7219
      max_thread_proc 3000
      nproc 4116 (Change this one before maxuprc)
      maxuprc 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
      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.

    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 WebSphere Application Server 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
  3. Verify that prerequisites and corequisites are at the required release levels.

Result

What to do next

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.




Related tasks
Preparing to install Network Deployment on an HP-UX system

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_hpuxsetup.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)