[AIX HP-UX Linux Solaris Windows]This topic applies only on the i5/OS operating system.

Installing a CIP

Install a customized installation package (CIP) for the feature pack.

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.

[Windows] The installation procedure requires the installer ID to have the following advanced user rights, Act as part of the operating system and Log on as a service to install Windows services.

[Windows] [Fix Pack 9 or later]
[Windows 7] [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] Guidelines for installing WebSphere Application Server on some Windows operating systems:

For more supported software information, see the WebSphere® Application Server detailed system requirements.

  • [Windows 7] [Fix Pack 29 or later] Support for WebSphere Application Server Version 6.1 on the Windows® 7 and Windows Server 2008 R2 operating systems began with WebSphere Application Server Version 6.1.0.29.
  • [Fix Pack 17 or later] Support for WebSphere Application Server Version 6.1 on the Windows Server 2008 operating system began with WebSphere Application Server Version 6.1.0.17.
  • [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Support for WebSphere Application Server Version 6.1 on the Microsoft® Windows Vista operating system began with WebSphere Application Server Version 6.1.0.9.

    See WebSphere Application Server support for the Microsoft Windows Vista operating system for detailed information on that support.

  • There are differences between the Windows 7, Windows Vista, Windows Server 2008 R2 and Windows 2008 operating systems and Windows 2008 operating system and previous Windows operating systems, particularly in the area of User Account Control (UAC). The following procedure should be followed when installing Websphere Application Server on a machine containing these operating systems.
    1. First, install Websphere Application Server Version 6.1.
      Perform your installation with an understanding of the differences between these operating systems and earlier Microsoft Windows operating systems. From the standpoint of Websphere Application Server installation and operation, one of the most significant changes for these operating systems is the introduction of UAC. UAC is enabled by default.
      • Choosing a user account

        Use the administrator account that was created when the operating system was installed to install WebSphere Application Server. This account is a member of the administrators group.

      • Choosing an installation location
        The following default installation directory is often used on other Windows operating systems:
        C:\Program Files\IBM\WebSphere\AppServer 
        However, WebSphere Application Server locates various log files and configuration files in the installation directory; and on the Windows 7, Windows Vista, Windows Server 2008 R2 and Windows 2008 operating systems, files located under the Program Files directory can only be created or modified by applications running with Administrator privileges. On a machine running these operating systems, therefore, you can install Websphere Application Server in the user directory of the administrator account. Typically, this would be similar to the following directory:
        C:\Users\administrator_account_name\IBM\Websphere\AppServer 

        You might have to manually override the default selection to install in the recommended location.

        If you are using a standard user account, which does not have Administrator privileges, do not use an installation path that contains the Program Files directory because only users with Administrative privileges can access that directory. You can install the product in another location as long as the user has access and permissions for that location. For example, you can use the following directories:
        • C:\Users\administrator_account_name\IBM
        • c:\IBM
        Note: Websphere Application Server icons and shortcuts are not created in the Windows Start menu for any users other than the Administrator if you install under the Program Files directory (which is not recommended in any case). You must install to a directory other than Program Files if you want to have Websphere Application Server icons and shortcuts created in the Start menus of users with standard privileges.
      • Installing silently
        Performing a silent installation of Version 6.1 on a machine running the Windows 7, Windows Vista, Windows Server 2008 R2 and Windows 2008 operating systems requires Administrator privileges.
        • If you launch the silent installation using standard user privileges, you are presented with an elevation prompt for Administrator privileges before you are allowed to continue.
          You can avoid this prompt by running the silent installation from a Command Prompt window that is opened by performing the following actions:
          • Right-click a Command Prompt shortcut.
          • Click Run As Administrator.
        • When you open the Command Prompt window as Administrator, an operating-system dialog appears that asks you if you want to continue. Click Continue to proceed.

        You might have to manually change the installLocation specification in your response file to point to the recommended installation directory.

      • Installing as a non-Administrator
        • If a non-Administrator tries to install Version 6.1 on a machine running the Windows 7, Windows Vista, Windows Server 2008 R2 and Windows 2008 operating systems using the original Version 6.1 media, the operating system does not install the application using the non-Administrator's account. The operating system will require that the non-Administrator change to an account with elevated (Administrator) privileges.
        • To allow a user to install WebSphere Application Server as a non-Administrator on a machine running the Windows Vista operating system, an appropriate manifest must exist in the install.exe files. The manifest tells the operating system that Administrator privileges are not required. This manifest does not exist in the install.exe files on the original media for Version 6.1.

          Complete the procedure found in A non-Administrator might not be able to install WebSphere Application Server on a Microsoft Windows Vista operating system to replace the install.exe files with files that contain an appropriate manifest and run the installation as a non-Administrator.

        • Non-Administrators must not try to install Version 6.1 under the Program Files directory (which is not recommended in any case) because installation in that directory requires Administrator privileges.
      • Performing runtime operations after installation
        Immediately after installing Version 6.1, do not attempt to perform any of the following runtime operations:
        • Launching the Websphere Application Server runtime
        • Verifying the installation
        • Using the Profile Management tool or the manageprofiles command to create profiles
    2. Download and install the appropriate version of the Update Installer for WebSphere Software from the product support Web site.

      See Recommended fixes for WebSphere Application Server for a link to the appropriate Update Installer download page and installation instructions.

      [Windows 7] [Fix Pack 29 or later] Download and install the Update Installer for WebSphere Software Version 7.0.0.9 or later from the product support Web site.

      [Fix Pack 17 or later] Download and install the Update Installer for WebSphere Software Version 6.1.0.17 or later from the product support Web site.

      [This information only applies to Version 6.1.0.9 and later running on the Microsoft Windows Vista operating system.] [Fix Pack 9 or later] Download and install the Update Installer for WebSphere Software Version 6.1.0.9 or later from the product support Web site.

      Supported configurations Supported configurations: You can use the Update Installer for WebSphere Software Version 7.0 to install the fix packs for Version 6.1.sptcfg
    3. Download and install the latest code for the IBM® Installation Factory for WebSphere Application Server.

      See IBM Installation Factory for WebSphere Application Server V6.1 releases for the Installation Factory download page.

      Use Install Factory to create CIP at desired level and then run the install.

      Note: This step is only necessary if you are making a CIP image using the IBM Installation Factory for WebSphere Application Server. In this case, use the following service packs as they apply to your Windows operating system:
      • WebSphere Application Server Version 6.1.0.9 or later applies to the Windows Vista operating system.
      • WebSphere Application Server Version 6.1.0.17 or later applies to the Windows 2008 operating system.
      • WebSphere Application Server Version 6.1.0.29 or later applies here to the Windows 2008 R2 and Windows 7 operating systems.
    4. If the Installation Factory cannot be used and the general availability version of WebSphere Application Server is used for the install on Windows 2008 and Windows 7, then the profile should not be created at the time of the install unless WebSphere Application Server is updated to the recommended level.
      • For BASE and EXPRESS installation

        Using silent install, add -OPT profileType="none" in the response file.

        Using GUI install, run install.exe/sh -OPT profileType="none" on the command line to launch the WebSphere Application Server installer.

      • For Network Deployment installation

        Using silent install, add -OPT profileType="none" in the response file.

        Using GUI install, select "none" on the WebSphere Application Server environment panel and click on "Yes" on the pop-up warning.

    5. Make sure that you are using IBM Java 2 Platform Standard Edition Development Kit (SDK) 1.5 Service Release 5 or later.
    6. Use the Update Installer for WebSphere Software Version 7.0 or later to install a service pack containing WebSphereApplication Server Version 6.1.0.9 or later.

      Specifically, for Windows 2008, install a service pack containing WebSphereApplication Server version 6.1.0.17 or later and for Windows 2008 R2 and Windows 7 install a service pack containing WebSphereApplication Server version 6.1.0.29 or later.

      Make sure that you use the same administrator account that you used for the Version 6.1 installation.

    7. You can now perform the following actions:

[AIX HP-UX Linux Solaris 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. For detailed information on non-root limitations see, Limitations of non-root installers.

Avoid trouble Avoid trouble:

As of Version 6.1.0.13 you must keep the version levels of the application server and any installed feature packs synchronized to the same maintenance level. If you have any feature packs installed, then it is recommended that you use the Update Installer to synchronize your environment before installing any additional Installation Factory packages. In fact, you will either be blocked from installing or prompted to upgrade during the installation of a feature pack CIP if your versions are not the same. If you are prompted and do not provide the proper maintenance packages you will be blocked from installing the CIP.

You can slip install, or update, an existing application server that contains one or more feature packs with an IIP as long as all packages in the IIP are at the same maintenance level. You can alsoscratch install an IIP containing the application server and one or more feature packs onto a machine with no existing application server as long as all included packages are at the same maintenance level. Read the Working with feature packs topic for more information. You must use Installation Factory version 6.1.0.17 or later if you want to use an IIP to update a feature pack environment.

If you are installing the Feature Pack for Web Services for the first time, then it is recommended that you create a CIP containing the feature pack and the most recent fix pack. Otherwise if you have already installed the Feature Pack for Web Services with the regular installer, you need to include a mandatory interim fix before installing a CIP containing any feature pack fix packs. See Installing and configuring multiple feature packs for additional information regarding feature pack installation and other considerations.gotcha

About this task

This topic describes how to install the product using a CIP. A CIP installation runs the installation wizard in graphical interface mode or in silent mode.

The installation wizard performs the following actions:
  • Automatically checks system prerequisites
  • Looks for a previous WebSphere Application Server Version 6.1 installation to determine whether you can add a feature pack to the existing application server product
  • Determines if additional WebSphere 6.1 fixes or fix packs need to be applied in addition to the feature pack to meet the minimum feature pack prerequisite levels. If the existing application server is not at the required version, the feature pack installer will apply fix packs to bring the application server up to the required version.
  • Installs the necessary product binaries
  • Optionally launches the Profile Management tool upon completion of the installation to create or augment a profile. See Augmentation rules and limitations for feature packs on non-z/OS operating systems for more information.

Installing fixes included with the CIP

If you have included any fixes in the CIP whose prerequisites are not satisfied, then the CIP installer will not install those fixes and will continue to run instead of failing. The result of the installation will be a partial success, which allows you to attempt to resolve fix problems individually. If you want the CIP installation to fail if any of the included fixes fail, add the following option to the command line when invoking the installer:
-W installIfixesAsListOfMaintenances.skipPrereqFailure=false

Procedure

  1. Plan your installation.

    [AIX HP-UX Linux Solaris Windows] See Planning the installation.

    [iSeries] See Task overview: installing.

  2. Prepare your operating platform for installation.

    You install a feature pack on top of a Version 6.1 WebSphere Application Server product installation. If you prepared your operating system for the Version 6.1 installation, no additional preparation is required to install a feature pack.

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

    [iSeries] See Preparing the operating system for installation.

  3. Install a feature pack on top of an existing Version 6.1 WebSphere Application Server installation.

    [iSeries] You cannot install a feature pack or interim fixes remotely using a CIP. You must run the CIP locally on your iSeries machine using the command-line interface.

    Choose an installation scenario:
    • Graphical user interface: Install a feature pack on top of a Version 6.1 installation using the installation wizard.

      The installation lets you select features to install.

      [AIX HP-UX Linux Solaris Windows] See Installing a feature pack CIP.

    • Command-line interface: Perform a silent installation.

      A silent installation requires you to edit the response file that contains all of your installation choices. After creating a valid response file, issue the install command with the -silent parameter and the -options parameter from a command window.

      See Installing a CIP silently.

      [iSeries] Use this option to install a feature pack. You must install a feature pack locally. To install the product and interim fixes using a CIP, you must run the CIP locally on your iSeries machine using the command-line interface.

    The installer program does not support the ISMP-console installation method at this time.

    If you encounter a problem such as needing more disk space or temporary space or missing system prerequisite packages on your system, cancel the installation, make the required changes, and restart the installation.

Results

You can install a feature pack CIP on top of an existing product installation.

What to do next

See Overview of migration, coexistence, and interoperability for information about migrating from a previous version of WebSphere Application Server.

See Fast paths for WebSphere Application Server for information about getting started deploying applications.




In this 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 Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 2:56:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tins_install_61_cip
File name: tins_install_61_cip.html