Preparing Solaris systems for installation

Follow this procedure to prepare a Solaris system for installation of WebSphere Process Server.

Before you begin

The installation uses an InstallShield for Multiplatforms (ISMP) wizard. You can also install the product silently. Silent mode is invoked at a command line with a parameter that identifies an options response file, which you edit before installing.

Why and when to perform this task

Use the following procedure to prepare the operating system for installation of WebSphere Process Server.

Steps for this task

  1. Log on as root.

    You cannot install the product correctly as a non-root user. If you create copies of the product CDs, do so as root. Copies made by non-root users do not preserve the correct file attributes and do not work.

  2. 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
  3. Optional: Install the Mozilla browser if it is not already installed. The Mozilla browser supports the Launchpad console. Download and install the Mozilla browser from http://www.mozilla.org.
  4. 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 commands:
    BROWSER=/usr/bin/mozilla
    export BROWSER
  5. Stop all Java processes on the machine on which you are installing the product that are related to WebSphere Application Server, WebSphere Application Server Network Deployment, or WebSphere Process Server.
  6. Stop any Web server process such as the IBM HTTP Server.
  7. Provide adequate disk space. See Required disk space for the space required to install WebSphere Process Server and related products.
  8. Set kernel values to support WebSphere Process Server.

    Several Solaris kernel values are typically too small for the product. See Setting kernel values on Solaris systems for instructions on how to set kernel values.

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

    Although the Installation Wizard checks for prerequisite operating system patches, review the prerequisite supported hardware and software for WebSphere Process Server if you have not already done so. To access this information, see WebSphere Process Server detailed system requirements at http://www.ibm.com/support/docview.wss?uid=swg27006205 and select the link to your version of WebSphere Process Server.

    For instance, Solaris 9 SPARC workstations require the following patches:
    • 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

    Refer to the documentation for non-IBM prerequisite and corequisite products to learn how to migrate to their supported versions.

  10. Verify that the system cp command is used, rather than the cp command provided by emacs or other freeware.

    If you install the product using a cp command that is part of a freeware package, rather than with the system cp command, 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 (where install_root represents the installation directory of WebSphere Process Server).

    Missing files can destroy required symbolic links. You must remove the freeware cp command from the PATH in order to install the WebSphere Process Server product successfully.

    If you have emacs or other freeware installed on your operating system, perform the following steps to identify which cp command is being used by the system, and to deactivate the freeware cp command if it is being used:

    1. Type which cp at the command prompt before running the installation program for the WebSphere Process Server product.
    2. If the resulting directory output includes freeware, remove the freeware directory from your PATH. For example, if the output is similar to .../freeware/bin/cp, remove the directory from the PATH.
    3. After you install WebSphere Process Server, add the freeware directory back to the PATH.
  11. Verify that the Java 2 SDK on your copies of the product CDs is functioning correctly.

    If you created your own product CDs from ISO images or by copying the actual CDs, perform the following steps to verify that the Java 2 SDK is working correctly.

    1. On your created product CD for WebSphere Process Server CD 1, navigate to the /mnt/JDK/repository/prereq.jdk/java/bin directory. To do this, issue the following command:
      cd /mnt/JDK/repository/prereq.jdk/java/bin
    2. Verify the Java 2 SDK version. To do this, issue the following command:
      ./java -version
      The command completes successfully with no errors when the Java 2 SDK is intact.
    3. Repeat this procedure on your created product CD for WebSphere Process Server CD 2.

Result

This procedure prepares the operating system for installation of WebSphere Process Server.

What to do next

After preparing the operating system, you can install WebSphere Process Server. See Installing the product for descriptions of the various installation alternatives available.


Terms of use |

Last updated: Tue Feb 21 17:47:11 2006

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)