[AIX HP-UX Linux Solaris Windows]This topic applies only on the IBM i operating system.

Installing an IIP

Install an integrated installation package (IIP) with the installation wizard

Before you begin

Before you use the installation tools, read this topic to prepare for installation and to learn about installation options. Also read the hardware and software requirements on the Supported hardware and software Web site to get started.

[AIX Solaris HP-UX Linux Windows] The installer ID can be a non-root user ID. However, some installation procedures might require the installer ID to be the root user. Please consider all of the included contributions as they relate to user type. For example, if you are using the root ID you may need to pass non-root user contribution options into a contribution you will need to use -iipUserType=nonroot. Read the "Non-root installation" topic for detailed information on general non-root limitations.

About this task

You must use the Installation Factory to create an IIP before you can install the IIP. See Developing and installing integrated installation packages for more information about creating an IIP. To install an IIP silently see Installing an IIP silently.

The installation wizard installs each contribution in the order which was defined by the user during IIP creation. Although the IIP installer does not perform any prerequisite checking, each contribution installer will perform its own checking and will fail if the machine has not met the system requirements for that product.

[iSeries] If an IIP contains multiple contributions which are capable of installing remotely to IBM® i (which is the case with several of the WebSphere® Application Server install packages), the user will need to authenticate with the remote system each time a contribution is invoked, instead of once for the entire IIP. If you are including a feature pack CIP, please note that you cannot install a feature pack or interim fixes remotely using a CIP. You must run the CIP locally on your IBM i machine using the command-line interface. Read the Installing a CIP using a Windows workstation graphical interface topic for more information on installing the product, without any fixes, remotely from a Windows® workstation.

Procedure

  1. Plan your installation.

    Read the "Planning the installation" topic.

  2. Prepare your operating platform for installation.

    You must prepare your operating system to install all of the various products which are in the IIP or a contribution might fail. Review the prerequisites for each product before installing the IIP. Please see System Requirements for WebSphere Application Server V6.1 for more information on prerequisites for the application server products.

    [AIX Solaris HP-UX Linux Windows] Read the "Preparing the operating system for product installation" topic.

    [iSeries] Read the "Preparing the operating system for installation" topic.

  3. Log on to the operating system. If you are installing as a non-root or non-administrative user, then there are certain limitations.
    [AIX] [HP-UX] [Linux] [Solaris] In addition, 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 could be used, depending on whether or not 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
    [Windows] When installing as an administrative user on a Windows operating system, a Windows service is automatically created to autostart the application server. The installer user account must have the following advanced user rights:
    • Act as part of the operating system
    • Log on as a service
    For example, on some Windows operating systems, click Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignments to set the advanced options. See your Windows operating system documentation for more information.

    [Windows] If you plan to run the application server as a Windows service, do not install from a user ID that contains spaces. A user ID with spaces cannot be validated. Such a user ID is not allowed to continue the installation. To work around this restriction, install with a user ID that does not contain spaces.

  4. Insert the CD or DVD with the IIP into the disc drive, or access the directory where the IIP is located. If the IIP is on disc, you must use the -iipLogFile parameter to redirect the log location because the installer will not be able to write a log to the media. See IIP installation options for the available installation command line and response file parameters.

    Mount the drive if necessary.

  5. Start the installation directly with the install command. Refer to the installation options referenced in step 4.
    [Solaris] Note: If you have previously encountered an error installing an IIP, you might not be able to successfully start the IIP GUI. Certain temporary files might remain from the previous installation attempt which could prevent you from launching the GUI. Delete the following directory manually, then retry the installation: user_home/.com.ibm.ws.install.iip. To determine the location of user_home, enter the command echo %USERPROFILE% on Windows operating systems, or enter the command echo $HOME on operating systems such as AIX or Linux.
  6. The installer wizard initializes and the Welcome panel is displayed.

    Click About to see information about the author, organization, version, and all included packages. Click Next.

  7. The Installation selection panel is displayed.

    This panel lists all of the contribution invocations in the IIP, and their properties, in the order that they will be invoked. You may only change certain properties of each contribution depending on whether the IIP creator decided to allow those user changes at runtime. The Description field beneath the contributions table is read-only and will change depending on which contribution is selected.

    • Installation name

      Specifies the installation name of the selected package. This is read only.

    • Status

      Specifies whether the package is selected to be installed or is deselected before installation based on whether the checkbox at the beginning of the row has been selected. Deselected packages are skipped by the IIP install wizard during installation. If you remove a package which is a prerequisite for another package then you are unable to install the next package. For example, if you deselect the application server package , then you are unable to install a feature pack if you have no existing application server on the machine in the target directory.

      This field also indicates the installation status of the package during and after installation. At the end of each installation, the status field shows whether the installation was successful. If it was not successful, the IIP will run the exit code action which you or the IIP creator specified for that package. The available status codes are the following:

      • Success

        The package installed successfully.

      • Fail

        The package failed to install.

      • Partial Success

        The package installed successfully, but certain post-installation scripts failed to complete successfully.

      • CanceledByUser

        The package installer was canceled by the user.

      • Unknown

        The package installer failed to complete successfully with unknown errors.

    • Installation mode

      Specifies whether the selected installation package installs interactively with a wizard or silently using the specified response file.

    • Installation directory

      Specifies the target installation directory for the selected installation package.

    • Response file directory path and file name

      Specifies the response file location for the selected installation package. A response file must be specified if you are installing the selected package silently.

    Select an invocation and click Modify to edit the properties which are available to you. Once you have modified all of the necessary options, click Install to begin the installation.

  8. The installation begins. You can track the status of each contribution with the Installation progress bar at the bottom of the panel. At the end of each installation, the status field shows whether the installation was successful. There is also a progress bar which shows the status of the overall IIP installation.

    If a contribution fails to install, then the IIP installer will perform one of three actions which you or the IIP creator specified for that contribution invocation that are associated with that exit code:

    Table 1. Exit code actions
    Action Description
    Ask user whether to stop or to continue the installation Control is returned to the IIP installer wizard and you are prompted to perform some action. For example, you can change the selection of remaining contributions to install, stop installing, or continue installing without changing the current package installation.
    Continue installing the integrated installation package The exit code will be ignored and the IIP installation process will continue to the next installation package invocation.
    Stop installing the integrated installation package The package installation process will be stopped and control is returned to the IIP installer.

    A contribution installation that is a partial success or has been cancelled by the user will return control to the IIP installer which will perform one of three actions associated with the exit code in Table 1. The default is Stop installing the integrated installation package unless specified otherwise during IIP creation.

    If you click Cancel on the IIP installation wizard at any time during the installation, the current package will continue installing until it is completed but the remaining contributions will not be installed. You can modify the remaining contributions and continue the installation or you can choose to exit the installation wizard. If you click Cancel before the installation of any packages, the installer will exit the wizard after prompting you with a confirmation dialog window.

  9. Click the View Log button next to the packages list to view the log for the selected package. You can also choose to browse for the log file and view it through a text editor of your choice. Please consult that product's documentation for log file locations.
    You can view the overall IIP log file by clicking the View Log button next to the installation status section. You can also view the log through a text editor of your choice by opening it directly:
  10. Click Finish to exit the installation wizard.

Results

You have installed an integrated installation package.

What to do next

Note: If an included contribution fails to install, you might need to edit that contribution's response file, which is different from the overall IIP response file. By default, contribution response files are located in IIP_home/ResponseFiles.

Read the "Fast paths for WebSphere Application Server" topic for information about getting started deploying applications.

[AIX Solaris HP-UX Linux Windows] Note: During IIP installation, workspace files that might contain crucial logging information from Eclipse are created in the following directory:
  • [Windows] %USERPROFILE%\.com.ibm.was.install.iip
  • [AIX] [HP-UX] [Linux] [Solaris] $HOME/.com.ibm.was.install.iip
You might want to manually delete these files periodically to free up disk space.



In this information ...


Related information

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    

Terms of Use | Feedback

Last updated: Oct 21, 2010 12:35:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=ifactory&topic=tins_if_iip_install
File name: tins_if_iip_install.html