Installing the product on distributed operating systems

You use IBM® Installation Manager to install this version of Websphere Load Balancer for IPv4 and IPv6.

Before you begin

New feature New feature:
Installation Manager is a single installation program that can use remote or local software flat-file repositories to install, modify, or update new WebSphere® Application Server products. It determines and shows available packages—including products, fix packs, interim fixes, and so on—checks prerequisites and interdependencies, and installs the selected packages. You also use Installation Manager to easily uninstall the packages that it installed. newfeat
Restrictions:
  • Do not use the same response files that are used with previous versions of Websphere Load Balancer for IPv4 and IPv6 to install or uninstall Version 8.5 silently. Use response files that are based on Installation Manager to install, update, or uninstall Version 8.5 and later.
  • [Solaris] When you install a product using Installation Manager with local repositories, the installation takes a significantly longer amount of time if you use a compressed repository file directly without extracting it.

    Before you install a product using local repositories, extract the compressed repository file to a location on your local system before using Installation Manager to access it.

  • [Linux] Installation Manager console mode, which is included in Installation Manager Version 1.4.3 and later, does not work with WebSphere Application Server Version 8.5 offerings on systems other than z/OS®.
Important: Do not transfer the content of a repository in non-binary mode and do not convert any content on extraction.
Tip: Although almost all of the instructions in this section of the information center will work with earlier versions of IBM Installation Manager, the information here is optimized for users who have installed or upgraded to Installation Manager Version 1.5 or later.
Important: Installation Manager can install any fix-pack level of the product directly without installing the interim fix packs; in fact, Installation Manager installs the latest level by default. For example, you can skip fix-pack levels and go from Version 8.5.0.1 directly to Version 8.5.0.5. Keep in mind, however, that later you can not roll back to any level that was skipped. If you directly install to Version 8.5.0.5, for example, you cannot roll back to Version 8.5.0.4. If you skip from Version 8.5.0.1 to Version 8.5.0.5, you can only roll back to Version 8.5.0.1. You should plan your installations accordingly.

About this task

Perform one of these procedures to install or uninstall the product using Installation Manager.

Procedure

Results

Notes on logging and tracing:
  • One way to view the logs is to open Installation Manager and go to File > View Log. You can open an individual log file 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:
    • [AIX][HP-UX][Linux][Solaris] Administrative installation:
      C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager
    • [Windows] Administrative installation:
      /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 Websphere Load Balancer for IPv4 and IPv6 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 Websphere Load Balancer for IPv4 and IPv6 plug-ins.
Notes on troubleshooting:
  • [HP-UX] When you attempt to launch Installation Manager from a DVD that was mounted using the CD-ROM file system (CDFS) on an HP-UX operating system, it might fail to launch and point to a log file that contains an exceptions similar to one of the following:
    java.util.zip.ZipException: Exception in opening zip file:
    org.osgi.framework.BundleException: Exception in 
    org.eclipse.update.internal.configurator.ConfigurationActivator.start() 
    or bundle org.eclipse.update.configurator.

    This issue might be caused by Installation Manager reaching the upper limit of number of descriptors that can be opened on a CDFS-mounted device. This upper limit is determined by the value for the tunable kernel parameter ncdnode, which specifies the maximum number of CDFS nodes that can be in memory at any given time. To resolve the problem, change the ncdnode system kernel setting to 250. If the problem persists, increase the setting.

  • [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 disableOSPrereqChecking=true to the config.ini file in IM_install_root/eclipse/configuration and 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.
  • 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:
    • [AIX][HP-UX][Linux][Solaris] Go to the documentation subdirectory in the directory where Installation Manager is installed, and open the readme.html file.
    • [Windows] Click Start > Programs > IBM Installation Manager > Release Notes.
  • If a fatal error occurs when you try to install the product, take the following steps:
    1. Make a backup copy of your current product installation directory in case IBM support needs to review it later.
    2. Use Installation Manager to uninstall everything that you have installed under the product installation location (package group). You might run into errors, but they can be safely ignored.
    3. Delete everything that remains in the product installation directory.
    4. Use Installation Manager to reinstall the product to the same location or to a new one.
Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 16, 2014 11:59 AM EDT
File name: tins_lbinstall.html