Installing Edge Components with IBM Installation Manager

IBM Installation Manager is a common installer for many IBM software products that you use to install this version of Edge Components.

New Feature: Edge Components Version 8.0 is the first full version of the product to be installed by Installation Manager rather than the programs that are based on InstallShield MultiPlatform (ISMP) or native packages that are used to install, update, and uninstall previous versions. Installation Manager is a single installation program that can use remote or local software flat-file repositories to install, modify, or update the products. It determines and shows available packages -- including products, fix packs, interim fixes, etc. -- checks prerequisites and interdependencies, and installs the selected packages. You also use Installation Manager to easily uninstall the packages that it installed.

Overview of IBM Installation Manager
IBM Installation Manager is a general-purpose software installation and update tool that runs on a range of computer systems. Installation Manager can be invoked through a graphical user interface (GUI) or a command-line interface. You can also create response files in XML and use them to direct the performance of Installation Manager tasks in silent mode. For more information on using Installation Manager, read the Installation Manager Information Center.
Packages and package groups
Each software product that can be installed with Installation Manager is referred to as a "package." An installed package has a product level and an installation location. A package group consists of all of the products that are installed at a single location.
Installation Manager modes
IBM Installation Manager can be installed in one of the following three modes:
How many Installation Managers do you need
You only need to run Installation Manager on those systems on which you install or update product code. You normally need only one Installation Manager on a system because one Installation Manager can keep track of any number of product installations.
Getting the Installation Manager installation kit
IBM Installation Manager comes in the form of an installation kit, which contains a set of Installation Manager binaries and a flat-file repository for the Installation Manager product. The installation kit is only used for setup and maintenance of the Installation Manager.
Installing Installation Manager
When the installation kit is available on your system, you can install Installation Manager. Installation Manager consists of a set of binaries that are copied from the installation kit and a set of runtime data that describe the products that have been installed by this particular Installation Manager. Before installing Installation Manager, you must decide in which mode the Installation Manager will run as well as where the binaries and runtime data -- called "agent data" or "appdata" -- will reside. Then, you issue the Installation Manager installc, userinstc, or groupinstc command from the appropriate user ID to install Installation Manager.
Accessing product repositories
All software materials that will be installed with IBM Installation Manager are stored in flat-file repositories. Each repository contains program objects and metadata for one or more packages--that is, software products at a particular level. Repositories can also contain product maintenance, such as fix packs and ifixes. Whenever you install a new product, you can choose from any of the available product levels in any accessible repository.
Installing the product
After you have installed Installation Manager and have access to all necessary product repositories, you can use Installation Manager command-line commands or response files to perform the actual product installations. When you install a product, you provide the package name, optionally the product level to be installed, the product location, and any other optional properties. For example, some products have optional features that you can select at installation time or a list of optional supported language packs from which you can select.
Working with installed products
You can use Installation Manager commands to list installed products and product levels. You can also obtain this information for installed copies of the products by issuing the versionInfo command from the product file system. You can use Installation Manager commands or response files to install a new product level, roll back to a previous level, or modify the product by adding or removing optional features or language packs.
Using the IBM Packaging Utility
With the Packaging Utility, you can create and manage packages for installation repositories. You can copy multiple packages into one repository or copy multiple disks for one product into a repository. You can copy packages from Passport Advantage into a repository, for example. For more information on the Packaging Utility, go to the IBM Installation Manager Version 1.4 Information Center or the IBM Installation Manager Version 1.5 Information Center.
Restrictions

New Feature: In addition to the GUI and silent methods described in this information, you can also use Installation Manager to manage installation using the Installation Manager imcl installation command. For information on using Installation Manager using this method, read the Installation Manager Information Center.

Perform the following tasks:

  1. Ensure that any previous versions of the product are uninstalled. You must uninstall previous versions of Edge Components through the native installation program or system package tools.

    Read Uninstalling previous versions of Edge Components for instructions.

  2. Perform the tasks in Installing IBM Installation Manager, which includes adding the product repositories for the Edge Components products.
  3. Install the product:
  4. To update your products, read Installing fix packs to Edge Components.

If you need to uninstall the product through IBM Installation Manager, perform one of the following tasks:

After installing the product, be aware of the following notes for logging, tracing, and troubleshooting:

Notes on logging and tracing
Notes on troubleshooting
Note on version and history information
The versionInfo and historyInfo commands return version and history information based on all of the installation, uninstallation, update, and roll back activities performed on the system.

Installing IBM Installation Manager

Before you install any Edge Components products, you need to install IBM Installation Manager.

  1. Obtain the necessary files from the physical media or the web. There are three basic options for obtaining and installing Installation Manager and the product.
  2. Install the product through the GUI or silently.
  3. Add the product repository to your Installation Manager preferences. There are three ways to access repositories for your product: To add the repository:
    1. Start Installation Manager.
    2. In the top menu, click File > Preferences.
    3. Select Repositories.
    4. Click Add Repository.
    5. Enter the path to the repository.config file in the location containing the repository files.
      • This is a sample path for a local repository:

        [Windows]

        C:\repositories\product_name\local-repositories

        [AIX] [HP-UX] [Linux] [Solaris]

        /var/repositories/product_name/local-repositories
      • This is the path for the remote repository:
        http://www.ibm.com/software/repositorymanager/V8WASNDEdge
        Note:
        Be aware of the following conditions:
        • You must have Administrator or root access to install and use Load Balancer for IPv4 and Caching Proxy.
        • [Windows]Do not install Caching Proxy on 64-bit operating systems.
        • [Windows] The default paths for Caching Proxy, Version 7 and earlier are different than the default paths for the current version. Update the local path in your configuration files to the new path after you migrate to the new version of Caching Proxy.
        • [Windows] Load Balancer for IPv4 is not supported on Windows 7 or Windows Vista.
        • [Windows] Before you install Load Balancer for IPv4 on Windows 2003 64-bit machines, you must install the required Microsoft hotfix. If you do not install the Microsoft hotfix prior to installing Load Balancer for IPv4, Load Balancer does not run correctly.

          To correct this problem, you must install the required Microsoft hotfix for KB942589. After you apply the Microsoft hotfix, restart your system. You must restart your system before you install Load Balancer for IPv4 on Windows 2003 64-bit machines. You will need to restart your system again after completing the installation of Load Balancer for IPv4.

          If you do not install the Microsoft hotfix before you install Load Balancer for IPv4 and you encounter this problem, you must uninstall Load Balancer for IPv4, install the Microsoft hotfix, and then reinstall Load Balancer for IPv4.

    6. Click OK.
    7. Deselect any locations listed in the Repositories window that you will not be using.
    8. Click Apply.
    9. Click OK.
    10. Click File > Exit to close Installation Manager.
  4. Install the Edge Components product:

Installing Edge Components with the IBM Installation Manager GUI

Use the Installation Manager GUI to install Edge Components products.

Note:
Be aware of the following conditions when you install this product:

  1. Installing IBM Installation Manager if it is not installed. These instructions also include steps to add repository information for the Edge Components products.
  2. Start Installation Manager.
  3. Click Install.
    Note:
    If you are prompted to authenticate, use the Passport Advantage credentials that you registered with on the program website. Installation Manager searches its defined repositories for available packages.
  4. Select the product you want to install. For example, select IBM WebSphere Edge Components: Caching Proxy or IBM WebSphere Edge Components: Load Balancer for IPv4.

    If you already have the product installed on your system, a message displays indicating that the product is already installed.

  5. Click Next.
    Note:
    If you try to install a newer level of the product with a previous version of Installation Manager, Installation Manager might prompt you to update to the latest level of Installation Manager when it connects to the repository. Update to the newer version before you continue if you are prompted to do so. Read the Installation Manager Information Center for information about automatic updates.
  6. Accept the terms in the license agreements, and click Next.
  7. Specify the installation root directory for the product binaries, which are also referred to as the core product files or system files.

    The panel also displays the shared resources directory and disk-space information.

    Note:
    The first time that you install a package using Installation Manager, specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. Use your largest drive for this installation. You cannot change the directory location until after you uninstall all packages.

    Restrictions:

  8. Click Next.
  9. Select the languages for which translated content should be installed. English is always selected.
  10. Click Next.
  11. Select the features that you want to install.
  12. Click Next.
  13. Review the summary information, and click Install.
  14. Click Finish.
  15. Click File > Exit to close Installation Manager.
  16. [Windows] Optional: If you are migrating from a previous version of Caching Proxy, update the configuration files with the new installation path. The default paths for Caching Proxy Version 7 and earlier are different than the default paths for the current version.

Tip: Installation Manager optionally can search for updates to itself whenever the Install Packages, Modify Packages, or Update Packages page is opened from the Start page as well as when clicking Check for Other Versions and Extensions on the Install Packages page. To enable this option, perform the following actions:

  1. Start Installation Manager.
  2. In the top menu, click File > Preferences.
  3. Select Updates.
  4. Select Search for Installation Manager updates.
  5. Click Apply.
  6. Click OK.

Do not enable this option if you do not have access to the service repository.

Installing Edge Components silently with IBM Installation Manager

Note:
Be aware of the following conditions when you install this product:
  1. Installing IBM Installation Manager if it is not installed. These instructions also include steps to add repository information for the Edge Components products.
  2. Optional: Record a response file to install the product. If you already have a response file, proceed directly to Step Use the response files to install the product silently..

    On one of your systems, perform the following actions to record a response file that will install the product:

    1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
    2. Start Installation Manager from the command line using the -record option. For example:
      • [Windows] Administrator or non-administrator:
        IBMIM.exe -skipInstall "C:\temp\imRegistry" 
          -record C:\temp\install_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./IBMIM -skipInstall /var/temp/imRegistry 
          -record /var/temp/install_response_file.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./IBMIM -skipInstall user_home/var/temp/imRegistry 
          -record user_home/var/temp/install_response_file.xml

      Tip: When you record a new response file, you can specify the -skipInstall parameter. Using this parameter has the following benefits:

      • No files are actually installed, and this speeds up the recording.
      • If you use a temporary data location with the -skipInstall parameter, Installation Manager writes the installation registry to the specified data location while recording. When you start Installation Manager again without the -skipInstall parameter, you then can use your response file to install against the real installation registry.
      • The -skipInstall operation should not be used on the actual agent data location used by Installation Manager. This is unsupported. Use a clean writable location, and re-use that location for future recording sessions

      For more information, read the Installation Manager Information Center.

    3. Ensure that you added the repository information for your product in Step 1.
    4. Click Install.
      Note:
      If you are prompted to authenticate, use the Passport Advantage credentials that you registered with on the program website. Installation Manager searches its defined repositories for available packages.
      Installation Manager searches its defined repositories for available packages.
    5. Select your product and the appropriate version. For example, select IBM WebSphere Edge Components: Caching Proxy or IBM WebSphere Edge Components: Load Balancer for IPv4.

      If you already have the product installed on a WebSphere Application Server installation on your system, a message displays indicating that the product is already installed. To create another installation of the product in another location, click Continue.

    6. Click Next.
    7. Accept the terms in the license agreements, and click Next.
    8. Specify the installation root directory for the product binaries, which are also referred to as the core product files or system files.

      The panel also displays the shared resources directory and disk-space information.

      Note:
      The first time that you install a package using Installation Manager, specify the shared resources directory. The shared resources directory is where installation artifacts are located that can be used by one or more package groups. Use your largest drive for this installation. You cannot change the directory location until after you uninstall all packages.

      Restrictions:

      • Installation manager requires that you install the product to an empty directory. The default installation paths are:
        Caching Proxy
        • [AIX] [HP-UX] [Linux] [Solaris]
          /opt/ibm/edge/
          This cannot be modified.
        • [Windows]
          C:\Program Files\IBM\edge\cachingproxy\
        Load Balancer for IPv4
        • [AIX] [HP-UX] [Linux] [Solaris]
          /opt/ibm/edge/lb/
          This cannot be modified.
        • [Windows]
          C:\Program Files\loadbalancer\IBM\edge\lb\
          The beginning of this installation path can be changed, but be aware that Installation Manager requires you to install the product into an empty directory - in the default path it is C:\Program Files\loadbalancer. The IBM\edge\lb portion of the path is hard coded and cannot be modified.
      • Deleting the default target location and leaving an installation-directory field empty prevents you from continuing.
      • Do not use symbolic links as the destination directory. Symbolic links are not supported.
      • Do not use a semicolon in the directory name. The product cannot install properly if the target directory includes a semicolon.
      • [Windows] A semicolon is the character used to construct the class path on Windows systems.
      • [Windows] The maximum path length on the Windows Server 2008, Windows Vista, and Windows 7 operating systems is 60 characters.
      • [Windows] Before you install Load Balancer for IPv4 on Windows 2003 64-bit machines, you must install the required Microsoft hotfix. If you do not install the Microsoft hotfix prior to installing Load Balancer for IPv4, Load Balancer does not run correctly.

        To correct this problem, you must install the required Microsoft hotfix for KB942589. After you apply the Microsoft hotfix, restart your system. You must restart your system before you install Load Balancer for IPv4 on Windows 2003 64-bit machines. You will need to restart your system again after completing the installation of Load Balancer for IPv4.

        If you do not install the Microsoft hotfix before you install Load Balancer for IPv4 and you encounter this problem, you must uninstall Load Balancer for IPv4, install the Microsoft hotfix, and then reinstall Load Balancer for IPv4.

    9. Click Next.
    10. Select the languages for which translated content should be installed. English is always selected.
    11. Click Next.
    12. Select the features that you want to install.
    13. Click Next.
    14. Review the summary information, and click Install.
      • If the installation is successful, the program displays a message indicating that installation is successful.
        Note:
        The program might also display important post-installation instructions as well.
      • If the installation is not successful, click View Log File to troubleshoot the problem.
    15. Click Finish.
    16. Click File > Exit to close Installation Manager.
    17. Optional: If you are using an authenticated remote repository, create a keyring file for silent installation.
      Note:
      In a keyring file, you can store credentials for URLs that require authentication, such as your remote repositories.
      1. From a command line, change to the eclipse subdirectory in the directory where you installed Installation Manager.
      2. Start Installation Manager from the command line using the -record option.

        For example:

        • [Windows] Administrator or non-administrator:
          IBMIM.exe -skipInstall "C:\temp\imRegistry" 
                -keyring C:\IM\im.keyring 
                -record C:\temp\keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
          ./IBMIM -skipInstall /var/temp/imRegistry 
                -keyring /var/IM/im.keyring 
                -record /var/temp/keyring_response_file.xml
        • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
          ./IBMIM -skipInstall user_home/var/temp/imRegistry 
                -keyring user_home/var/IM/im.keyring 
                -record user_home/var/temp/keyring_response_file.xml
      3. When a window opens that requests your credentials for the authenticated remote repository, enter the correct credentials and save them.
      4. Click File > Exit to close Installation Manager.

        For more information, read the Installation Manager Information Center.

  3. Use the response files to install the product silently.
    1. Optional: Use the response file to install the keyring file silently: Go to a command line on each of the systems on which you want to install the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the keyring file silently.

      For example:

      • [Windows] Administrator or non-administrator:
        imcl.exe -acceptLicense 
          input C:\temp\keyring_response_file.xml 
          -log C:\temp\keyring_log.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./imcl -acceptLicense 
          input /var/temp/keyring_response_file.xml 
          -log /var/temp/keyring_log.xml
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./imcl -acceptLicense 
          input user_home/var/temp/keyring_response_file.xml 
          -log user_home/var/temp/keyring_log.xml

      For more information on keyring files, read the Installation Manager Information Center.

    2. Use the response file to install the product silently. Go to a command line on each of the systems on which you want to install the product, change to the eclipse/tools subdirectory in the directory where you installed Installation Manager, and install the product silently.

      For example:

      • [Windows] Administrator or non-administrator:
        imcl.exe -acceptLicense 
              input C:\temp\install_response_file.xml 
              -log C:\temp\install_log.xml 
              -keyring C:\IM\im.keyring
      • [AIX] [HP-UX] [Linux] [Solaris] Administrator:
        ./imcl -acceptLicense 
              input /var/temp/install_response_file.xml 
              -log /var/temp/install_log.xml 
              -keyring /var/IM/im.keyring
      • [AIX] [HP-UX] [Linux] [Solaris] Non-administrator:
        ./imcl -acceptLicense 
              input user_home/var/temp/install_response_file.xml 
              -log user_home/var/temp/install_log.xml 
              -keyring user_home/var/IM/im.keyring

      Notes:

      • The relevant terms and conditions, notices, and other information are provided in the license-agreement files in the lafiles or product_name/lafiles subdirectory of the installation image or repository for this product.
      • The program might write important post-installation instructions to standard output.
  4. [Windows] Optional: If you are migrating from a previous version of Caching Proxy, update the configuration files with the new installation path. The default paths for Caching Proxy Version 7 and earlier are different than the default paths for the current version.

[Windows] Example: The following is a sample response file for installing Load Balancer for IPv4:

<?xml version="1.0" encoding="UTF-8"?>
<agent-input acceptLicense='true'>
<server>
<repository location='C:\repositories\edge80\local-repositories'/>
</server>
<profile id='Load Balancer for IPV4 v8.0' 
   installLocation='c:\program files\loadbalancer\ibm\edge\lb'>
<data key='eclipseLocation' value=c:\program files\loadbalancer\ibm\edge\lb'/>
<data key='user.import.profile' value='false'/>
<data key='cic.selector.nl' value='cs,ja,es,zh_HK,en,zh_TW,pt_BR,it'/>
</profile>
<install modify='false'>
<offering id='com.ibm.websphere.EDGELBIPV4.v80' version='8.0.0.0' 
   profile='IBM WebSphere Edge Components: Load Balancer for IPV4 V8.0' 
   features='Dispatcher,Load Balancer,Metric Server'/>
</install>
<preference name='com.ibm.cic.common.core.preferences.eclipseCache' 
   value='C:\Program Files\IBM\IMShared'/>
<preference value='30' name='com.ibm.cic.common.core.preferences.connectTimeout'/>
<preference value='30' name='com.ibm.cic.common.core.preferences.readTimeout'/>
<preference value='0' name='com.ibm.cic.common.core.preferences.downloadAutoRetryCount'/>
<preference value='false' name='offering.service.repositories.areUsed'/>
<preference value='false' name='com.ibm.cic.common.core.preferences.ssl.nonsecureMode'/>
<preference value='false' 
   name='com.ibm.cic.common.core.preferences.http.disablePreemptiveAuthentication'/>
<preference value='true' 
   name='com.ibm.cic.common.core.preferences.preserveDownloadedArtifacts'/>
<preference value='false' name='PassportAdvantageIsEnabled'/>
<preference value='false' 
   name='com.ibm.cic.common.core.preferences.searchForUpdates'/>
</agent-input>

Tips: