Install IBM HTTP Server on distributed systems with Installation Manager

We can install IBM Installation Manager silently, or with a user interface. IBM Installation Manager is a common installer for many IBM software products that we can use to install, update, roll back, and uninstall IBM HTTP Server.


Before you begin

Beginning with fix pack 9.0.5.4, if you are installing IBM HTTP Server on the Windows operating system for the first time, the installation is for a 64-bit runtime only. We cannot install a 32-bit runtime. If you installed IBM HTTP Server on the Windows operating system before fix pack 9.0.5.4, and then install it again with fix pack 9.0.5.4 or a later fix pack, the runtime by default stays at a 32-bit runtime. We can force the installation to be a 64-bit runtime by setting the was.install.internal.property.windows.install.64bit.ihs Installation Manager property to a value of true in the IM_install_root/eclipse/configuration/config.ini file before you start the installation. To return to a 32-bit runtime, you must install one of the fix packs before fix pack 9.0.5.4.

We can install IBM HTTP Server by using an archive install without the IBM Installation Manager. See Install and configure IBM HTTP Server from an archive for more information.

Before we can successfully install IBM HTTP Server, ensure that your environment meets the prerequisites for the application server. For more information, see the Preparing the operating system for product installation topic.

For transitioning users: IBM SDK, Java™ Technology Edition, Version 8 is the Java SDK version for WebSphere® Application Server Version 9.0. IBM SDK, Java Technology Edition is no longer embedded with IBM HTTP Server for WebSphere Application Server. The Java SDK is available as a separate offering that must be installed when you install IBM HTTP Server.


Procedure


Results

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:

    • Administrative installation: 
      C:\Documents and Settings\All Users\Application Data\IBM\Installation Manager

    • Non-administrative installation: 
      C:\Documents and Settings\user_name\Application Data\IBM\Installation Manager

    • Administrative installation: 
      /var/ibm/InstallationManager

    • 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.

Notes on troubleshooting:

  • 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.

    We 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.

  • Installation Manager might display a warning message during the uninstallation process.

    Uninstall IBM HTTP Server using Installation Manager requires that the data repositories remain valid and available.

    A warning message is displayed by Installation Manager to alert you when repositories are not available or connected. A similar warning message might display after you add or modify data repository connection preferences in Installation Manager.

    If Installation Manager detects missing data repositories or fails to connect to repositories during the uninstallation process, complete the following actions:

    1. Click Cancel to end the uninstallation task.

    2. Select File > Preferences > Repositories, and add the appropriate data repositories that we can connect to successfully.

    3. Exit Installation Manager.

    4. Restart Installation Manager.

    5. Uninstall IBM HTTP Server.

  • For more information on using Installation Manager, read the IBM Installation Manager documentation. Read the release notes to learn more about the latest version of Installation Manager. To access the release notes, complete the following task:

    • Click Start > Programs > IBM Installation Manager > Release Notes.

    • Go to the documentation subdirectory in the directory where Installation Manager is installed, and open the readme.html file.


Related concepts


Related tasks