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:
  • In admin mode, the Installation Manager is installed from an administrator or a root ID and can be invoked by any administrator or root user. Load Balancer for IPv4 requires you to install and run the program in admin or root mode for the processes to run.
  • In nonAdmin mode (also called "user mode"), only the user that installed Installation Manager can invoke it.
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
  • Do not use the same response files that are used with other versions of the product to install or uninstall Version 8.0 silently. Use response files that are based on Installation Manager to install, update, or uninstall Version 8.0 and later.
  • [Solaris] The Installation Manager GUI is not supported on Solaris 10 x64 systems. Perform the following actions to install or uninstall the product on these systems:
    1. Use the Installation Manager GUI on a supported system to record a response file that will allow you to install or uninstall the product silently.
    2. Edit the recorded response file if necessary.
    3. Use the response file to install or uninstall the product silently on your system.
  • [Linux] For any Linux system that is enabled for Security Enhanced Linux (SELinux), such as Red Hat Enterprise Linux Version 5 or SUSE Linux Enterprise Server Version 11, you must identify the Java shared libraries in the Installation Manager 1.4.2 or later installation image to the system. Also, you must identify the Java shared libraries in the Installation Manager 1.4.2 or later installation after it has been installed. For example:
    chcon -R -t texrel_shlib_t ${IM_Image}/jre_5.0.3.sr8a_20080811b/jre/bin
    chcon -R -t texrel_shlib_t 
         ${IM_Install_root}/eclipse/jre_5.0.3.sr8a_20080811b/jre/bin 
  • [Windows] If a non-administrator installs the product on a Windows Vista, Windows 7, or Windows Server 2008 operating system into the Program Files or Program Files (x86) directory with User Account Control (UAC) enabled, the product might not function correctly.

    UAC is an access-control mechanism that allows non-administrative users to install a software product into the Program Files or Program Files (x86) directory; but it then prohibits any write access to that directory after the installation has completed. The product requires write access in the main installation directory to function correctly.

    To resolve this issue, perform one of the following actions:

    • Install the product into a directory other than Program Files or Program Files (x86). For example:
      C:\IBM\Edge
    • Disable UAC.
  • When you install the product using Installation Manager with local repositories, the installation takes a significantly longer amount of time if you use the repository.zip file directly without extracting it.

    Before you install the product using Installation Manager local repositories, extract the repository.zip file to a location on your local system and add that location to your Installation Manager preferences.

    Note:
    Do not transfer the content of a repository in non-binary mode and do not convert any content on extraction.

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
  • An easy way to view the logs is to open Installation Manager and go to File > View Log. An individual log file can be opened by selecting it in the table and then clicking the Open log file icon.
  • Logs are located in the logs directory of Installation Manager's application data location. For example:
    • [Windows] Administrative installation:
      C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
    • [Windows] Non-administrative installation:
      C:\Documents and Settings\user_name\Application Data\IBM\Installation Manager
    • [AIX] [HP-UX] [Linux] [Solaris] Administrative installation:
      /opt/IBM/InstallationManager
    • [AIX] [HP-UX] [Linux] [Solaris] Non-administrative installation:
      user_home/var/ibm/InstallationManager
  • The main log files are time-stamped XML files in the logs directory, and they can be viewed using any standard web browser.
  • The log.properties file in the logs directory specifies the level of logging or tracing that Installation Manager uses. To turn on tracing for the Edge component plug-ins, for example, create a log.properties file with the following content:
    com.ibm.ws=DEBUG
    com.ibm.cic.agent.core.Engine=DEBUG
    global=DEBUG
    Restart Installation Manager as necessary, and Installation Manager outputs traces for the Edge component plug-ins.
Notes on troubleshooting
  • Set permissions of files that are installed into the /usr directory as 755. Files in the install_home directory depend on the system umask.
  • [HP-UX] By default, some HP-UX systems are configured to not use DNS to resolve host names. This could result in Installation Manager not being able to connect to an external repository. You can ping the repository, but nslookup does not return anything.

    Work with your system administrator to configure your machine to use DNS, or use the IP address of the repository.

  • In some cases, you might need to bypass existing checking mechanisms in Installation Manager.
    • On some network file systems, disk space might not be reported correctly at times, and you might need to bypass disk-space checking and proceed with your installation.

      To disable disk-space checking, specify the following system property in the config.ini file in IM_install_root/eclipse/configuration and restart Installation Manager:

      cic.override.disk.space=sizeunit

      where size is a positive integer and unit is blank for bytes, k for kilo, m for megabytes, or g for gigabytes. For example:

      cic.override.disk.space=120 (120 bytes)
      cic.override.disk.space=130k (130 kilobytes)
      cic.override.disk.space=140m (140 megabytes)
      cic.override.disk.space=150g (150 gigabytes)
      cic.override.disk.space=true

      Installation Manager will report a disk-space size of Long.MAX_VALUE. Instead of displaying a very large amount of available disk space, N/A is displayed.

    • To bypass operating-system prerequisite checking, add the following line to the to the config.ini file in IM_install_root/eclipse/configuration directory:
      disableOSPrereqChecking=true
      Then restart Installation Manager.
    If you need to use any of these bypass methods, contact IBM Support for assistance in developing a solution that does not involve bypassing the Installation Manager checking mechanisms.
  • Installation Manager might display a warning message during the uninstallation process.

    Uninstalling the product using Installation Manager requires that the data repositories remain valid and available.

  • For more information on using Installation Manager, read the IBM Installation Manager Information Center. Read the release notes to learn more about the latest version of Installation Manager.

    To access the release notes, complete the following task:

    • [Windows] Click Start > Programs > IBM Installation Manager > Release Notes.
    • [AIX] [HP-UX] [Linux] [Solaris] Go to the documentation subdirectory in the directory where Installation Manager is installed, and open the readme.html file.
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.