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

Preparing AIX systems for installation

This topic describes how to prepare an AIX system for the installation of IBM WebSphere Application Server products.

Before you begin

Why and when to perform this task

Steps for this task

  1. Use the System Management Interface Tool (SMIT) to display packages that are installed to determine whether you must update packages that are described in the following steps.
  2. Download the most current version of the INFOZIP product to avoid problems with zipped files. Although zipped files are primarily used in the service stream, prepare your AIX operating system by downloading a current version of the INFOZIP package from the http://www.info-zip.org Web site.
  3. Install the prerequisite xlC.rte 6.0 run-time code on AIX 5.2 maintenance level 1.

    You must install the xlC.rte 6.0 run-time code before you install the Global Security Kit (GSKit). The GSKit is installed as part of the installation of the IBM HTTP Server or as part of the installation of Web server plug-ins for WebSphere Application Server.

    Download the xlC.rte run-time code as a fix from the AIX Support site.

    If you have AIX 5.2, you can install the xlC.rte 6.0 run-time code from the AIX 5.2 CD.

  4. Provide adequate disk space.
    With the JFS file system on AIX, you can allocate expansion space for directories. If the Installation wizard does not have enough space, ISMP issues a system call for more space that increases the space allocation dynamically. The message you might see when this occurs for the /usr directory is similar to the following example:
    NOTE: The following file systems will be expanded during the installation:
      /usr
    Attention:
    730 MB for the /usr/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
    830 MB total requirement
    110 MB for the /usr/IBMIHS directory
    35 MB for the /usr/ibm/gsk7 directory

    The run-time module is gskkm.rte.

    200 MB for the /usr/IBM/WebSphere/plugins directory
    25 MB for the /usr/ibm/gsk7 directory
    The following space is required for the WebSphere Application Server Clients:
    150 MB for the /usr/IBM/WebSphere/AppClient directory
  5. Unmount file systems with broken links to avoid java.lang.NullPointerException errors.

    Unmount file systems with broken links before installing.

    Installation can fail with the following error when broken links exist to file systems:
    An error occurred during wizard bean change notification:
    java.lang.NullPointerException 
      at com.ibm.wizard.platform.aix.AixFileUtils.
         getFileSystemData(AixFileUtils.java:388)
      at com.ibm.wizard.platform.aix.AixFileUtils.
         getPartitionDataWithExecs(AixFileUtils.java:172)
      at com.ibm.wizard.platform.aix.AixFileUtils.
         getPartitionData(AixFileUtils.java:104)
      at com.ibm.wizard.platform.aix.AixFileServiceImpl.
         getPartitionNames(AixFileServiceImpl.java:397)
    ...
    
    Use the df -k command to check for broken links to file systems. Look for file systems that list blank values in the 1024-blocks size column. Columns with a value of "-" (dash) are not a problem. The following example shows a problem with the /dev/lv00 file system:
    >  df -k
    Filesystem    1024-blocks      Free %Used    Iused %Iused Mounted on
    /dev/hd4          1048576    447924   58%     2497     1% /
    /dev/hd3          4259840   2835816   34%      484     1% /tmp
    /proc                   -         -    -         -     -  /proc
    /dev/lv01         2097152    229276   90%     3982     1% /storage
    /dev/lv00
    /dev/hd2          2097152    458632   79%    42910     9% /usr
    iw031864:/cdrom/db2_v72_eee_aix32_sbcs
    
    The /proc file system is not a problem. The iw031864:/cdrom/db2_v72_eee_aix32_sbcs file system is a definite problem. The /dev/lv00 file system is also a likely problem. Use one of the following commands to solve this problem:
    >  umount /cdrom/db2_v72_eee_aix32_sbcs
    >  umount /cdrom 

    Start the installation again. If the problem continues, unmount any file systems that have blank values, such as the /dev/lv00 file system in the example. If you cannot solve the problem by unmounting file systems with broken links, reboot the machine and start the installation again.

  6. 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 already done so.

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

  7. [Version 6.0.2]64-bit V6.0.2 only: Apply the proper service level required for 64-bit exploitation support.

    Beginning with V6.0.2, WebSphere Application Server offers 64-bit exploitation support for 64-bit AIX 5L kernels. Order the V6.0.2 package to obtain the product media, or download the installation image from the Passport Advantage site.

    Before installing the 64-bit V6.0.2 WebSphere Application Server, upgrade AIX 5L 5.2 to maintenance level 6 (5200-06) or upgrade AIX 5L 5.3 to maintenance level 2 (5300-02). Otherwise, the installation can fail.
    • AIX 5L 5.3 maintenance level 5300-02
    • AIX 5L 5.2 maintenance level 5200-06

    See the AIX Fix Central Web site for more information.

  8. [Version 6.0.2]64-bit V6.0.2 only: Verify that the Java 2 SDK on the installation image can run.
    A known SDK conflict occurs when you have the following setting in your profile:
    LDR_CNTRL=MAXDATA
    The SDK does not run. The following command or any command fails:
    ./java -version
    Delete the LDR_CNTRL setting from your user_root/.profile file. Then log off and back on to pick up the new environment. Or export a null setting to flush the old setting:
    EXPORT LDR_CNTRL=

    Verify that the ./java -version command works. The command completes successfully with no errors when the Java 2 SDK is running.

  9. Optional: Install the Mozilla browser if it is not already installed. The Mozilla browser supports the launchpad console.
    1. Use smit to see if the Mozilla 1.4 or 1.7.8 or later package is already installed.
    2. Download two prerequisites from the AIX Toolbox for Linux Applications (glib & gtk+). Download the packages from the following locations:
    3. Install the packages after downloading them: Use the following command:
      rpm -Uvh glib-1.2.10-2.aix4.3.ppc.rpm gtkplus-1.2.10-4.aix5.1.ppc.rpm
      
    4. Download the latest supported version of Mozilla (1.7.8 or later) for AIX. Download Mozilla for AIX from the following location:

      http://www.ibm.com/servers/aix/browsers/

      Download the installp image and install it from smit.

      The Mozilla images distributed on the http://www.mozilla.org Web site are not provided by IBM. IBM has not tested and does not support the download from the non-IBM Web site. Download the Mozilla images from the IBM Web site to verify that the version that you download is tested and supported.

      [Version 6.0.2]Using Mozilla 1.7.5 or earlier can result in ISMP failing to initialize during installation. The launchpad link might seem to fail, for example. See V6.0.2: The WebSphere Application Server launchpad fails with Mozilla 1.7.5 (and earlier) on 64-bit AIX 5.2 or 5.3 for more information.

  10. 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=/usr/bin/mozilla
  11. Silent installation only: Make an allowance for a known ISMP problem that causes a call to the Xwindows service during a silent installation.
    The DISPLAY environment variable on your AIX machine might point to an X server that is not logged in. Two common scenarios can cause this to occur:
    • Your AIX machine has an X server running, but the X server is stuck at the graphical login screen because you have not yet logged in.
    • Your AIX machine is configured to display X Windows applications on a remote X server that is not logged in.

    A silent installation can hang in either case as ISMP calls Xwindows services.

    Two solutions exist:
    • Login to the local X server through the graphical user interface before beginning the silent installation.
    • Export the DISPLAY environment variable to point to null or blank.
      EXPORT DISPLAY=null

Result

What to do next

See Preparing to install Network Deployment on an AIX 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 AIX 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_aixsetup.html

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