[Fix Pack 25 or later]
[Linux only]

Preparing SUSE Linux Enterprise Server 11 for installation

This topic describes the steps that are needed to prepare the SUSE Linux® Enterprise Server Version 11 operating system prior to installing IBM® WebSphere® Application Server.

About this task

The SUSE Linux Enterprise Server Version 11 operating system was not available when WebSphere Application Server Version 6.1 originally shipped. Complete the following steps, which are common to any Linux operating system:

Procedure

  1. Log on to the operating system.

    You can log on as root or as a non-root 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 non-root 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
  2. Ensure that the Mozilla Firefox 3 browser on your SUSE Linux Enterprise Server Version 11 system is functional prior to installing WebSphere Application Server. The Mozilla Firefox 3 browser is bundled with SUSE Linux Enterprise Server Version 11.
    Note: It might be necessary to run >firefox &url from directories other than the one where Firefox is installed, so ensure that Firefox is in the path. You can add a symbolic link to the /opt/bin directory by entering:
    >ln -s /locationToFirefox/firefox firefox
  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.

    If the Firefox package is in the /usr/lib64/firefox directory, for example, use the following command:
    export BROWSER=/usr/lib64/firefox
  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:

    730 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, you must 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.

    830 MB total requirement

    This amount is the total space requirement when installing the product from the disc and when not installing service. Installing profiles requires more space.

    The IBM HTTP Server product requires the following space:

    763 MB total requirement
    This estimate includes:
    • The /opt/IBM/HTTPServer directory
    • The IBM Global Security Kit (GSKit) /opt/ibm/gsk7 directory
      Note: The GSKit runtime module is gsk7bas.i386.rpm for Linux distributed platforms and gsk7bas.s390.rpm for Linux for System z platforms.
    • The Web server plug-ins for WebSphere Application Server, including the /opt/IBM/WebSphere/plugins directory

    The IBM WebSphere Application Server Clients product requires the following space:

    150 MB for the app_client_root 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 Update Installer requires the following space:

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

    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. 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 Supported hardware and software Web site 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.

  8. Increase the ulimit setting in the bash command shell profile to prevent addNode and importWasprofile problems.

    The addNode command script can fail when adding a node, or the importWasprofile command can fail when importing a configuration archive. The importWasprofile command might fail during the installation of a customized installation package (CIP) when the CIP includes a customized profile.

    Set a higher ulimit setting for the kernel in the bash shell profile script, which is loaded at login time for the session.

    Set the ulimit on your Linux command shells by adding the command to your shell profile script. The shell profile script is usually found under your home directory:
    1. cd ~
    2. vi .bashrc
    3. ulimit -n 8192

    See http://www.ibm.com/support/docview.wss?uid=swg21223909 for more information.

  9. Restore the original copy of the /etc/issue file if the file is modified.

    The prereqChecker program in the installation wizard uses the file to verify the version of the operating system. If you cannot restore the original version, ignore the Operating System Level Check message about the operating system being unsupported. The installation can continue successfully despite the warning.

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

What to do next

You might have to complete additional steps to prepare a SUSE Linux Enterprise Server Version 11 system for a WebSphere Application Server installation. The following list contains information on the special installation considerations to avoid known issues.
  • To install the product silently, either set the disableOSPrereqChecking option to "true" in the response file or follow the instructions in the following technote to ensure a successful installation: WebSphere Application Server might not recognize SUSE Linux Enterprise Server 11 as a supported operating system.
  • For the 32-bit SUSE Linux Enterprise Server Version 11 operating system, the xorg-x11-libs package must be present prior to installing and using WebSphere Application Server.

    For more information on this package, see the Novell Web site.

  • For the 64-bit SUSE Linux Enterprise Server Version 11 operating system, both the xorg-x11-libs package and the xorg-x11-libs-32bit package must be present prior to installing and using WebSphere Application Server.

    For more information on this package, see the Novell Web site.

For additional information on known issues with WebSphere Application Server on this operating system, see the technotes, which are available on the IBM Support site.

After you complete the steps in this topic, proceed to the final step in Preparing Linux systems for installation.




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=tins_linuxsetup_sles11
File name: tins_linuxsetup_sles11.html