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

Preparing Solaris systems for installation

This topic describes how to prepare Solaris systems 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

  1. Log on as root.

    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.

    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 you can 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 Express product requires the following disk space:

    930 MB for the /opt/IBM/WebSphere/AppServer directory

    The installation root directory includes the core product files. This size includes the Sample applications. This size includes space for the default Application Server profile for the server1 process. The requirement does not include space for applications that you might install.

    Each Application Server profile requires approximately 200 MB plus 40 MB of temp space, and space for any applications that you develop and deploy.

    100 MB for the /tmp directory

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

    1030 MB total requirement

    This amount is the total space requirement when installing the product from the CD.

    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 Tivoli Global Security Kit requires this space.

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

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

    The Web server plug-ins require this space.

    35 MB for the /opt/ibm/gsk7 directory

    The Tivoli Global Security Kit requires this space.

    The following space is required for the IBM WebSphere Application Server 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 Version 4.0.x: The size of enterprise archive (EAR) files
    • For Version 5.0.x: The size of EAR files
  7. [Linux][UNIX]Set kernel values to support Application Server. Several Solaris kernel values are typically too small.
    Before installing, review the machine configuration:
    sysdef -i
    The kernel values are set in the /etc/system file, as shown in the following example.
    set shmsys:shminfo_shmmax = 4294967295
    set shmsys:shminfo_shmseg = 1024
    set shmsys:shminfo_shmmni = 1024
    set semsys:seminfo_semaem = 16384
    set semsys:seminfo_semmni = 1024
    set semsys:seminfo_semmap = 1026
    set semsys:seminfo_semmns = 16384
    set semsys:seminfo_semmsl = 100
    set semsys:seminfo_semopm = 100
    set semsys:seminfo_semmnu = 2048
    set semsys:seminfo_semume = 256
    set msgsys:msginfo_msgmap = 1026
    set msgsys:msginfo_msgmax = 65535
    set rlim_fd_cur=1024
    

    You can change kernel values by editing the /etc/system file then rebooting the operating system. For more information about setting up the Solaris system, see the Solaris System Administration documentation. For example, the Solaris Tunable Parameters Reference Manual.

    Queue managers are generally independent of each other. Therefore system kernel parameters, for example shmmni, semmni, semmns, and semmnu need to allow for the number of queue managers in the system.

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

    Solaris 9 SPARC workstations require the following patches to fix certain :
    • 112874-16 SunOS 5.9: patch libc
    • 113319-12 SunOS 5.9: libnsl nispasswdd patch
    • 115545-01 SunOS 5.9: nss_files patch
    • 115542-01 SunOS 5.9: nss_user patch
    • 115544-01 SunOS 5.9: nss_compat patch
    Solaris 8 SPARC workstations require the following patches to fix certain :
    • 115827-01 SunOS 5.8: /sbin/sulogin and /sbin/netstrategy patch
    • 115583-01 SunOS 5.8: /usr/lib/nss_user.so.1 patch
    • 108820-02 SunOS 5.8: nss_compat.so.1 patch
    • 113648-02 SunOS 5.8: /usr/sbin/mount patch
    • 108993-27 SunOS 5.8: LDAP2 client, libc, libthread and libnsl libraries patch
    • 108528-24 SunOS 5.8: kernel update patch

    Refer to the IBM WebSphere Application Server supported hardware, software, and APIs Web site for a complete list of required patches and to determine whether your operating system is supported when you receive a message from the prereqChecker program. The Web site lists all supported operating systems and the operating system fixes and patches that you must install to have a compliant operating system.

  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 WebSphere Application Server 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 WebSphere Application Server 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, you can 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, you can install the WebSphere Application Server product.

See Preparing to install the Express product on a Solaris system for the next step in the overall procedure, which is selecting the type of installation to perform.




Related tasks
Preparing to install the Express product on a Solaris system

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tins_solsetup.html

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