[AIX Solaris HP-UX Linux Windows]

Installing IBM HTTP Server from an archive

You can install IBM® HTTP Server (IHS) and the WebSphere® Application Server WebServer Plug-in by using an alternative installation method. With this fix pack, you do not need the IBM Installation Manager.

Before you begin

Obtain the IBM HTTP Server archive from Fix Central. The archive file name is specific to the operating system and architecture. File names begin with 9.0.0-WS-IHS-ARCHIVE. See the following example: 9.0.0-WS-IHS-ARCHIVE-linux-x86_64-FP006.zip.

For 9.0.0.7 and later, the file extension was changed from .tar.gz to .zip.

About this task

The IBM HTTP Server archive installation resembles a traditional installation of IBM HTTP Server and the WebServer Plug-in with a few of the following exceptions:
  • IBM Installation Manager is not used.
  • The WebSphere Configuration Tool and Plug-in Configuration Tool are not used.
  • IBM HTTP Server and the WebSphere Application Server Plug-ins share a single installation root.
  • No IBM Java™ is included, and the bin/ikeyman file and the bin/gskcmd file use your provided $JAVA_HOME.

Procedure

  1. Install IBM HTTP Server from the archive installation.
    1. Unpack the archive into your directory.
      1. Transfer the archive, such as 9.0.0-WS-IHS-ARCHIVE-linux-x86_64-FP006.zip, to the target system.
      2. Log in to the target system as the user ID that is used to start IHS, usually as root or as Administrator on Windows.
      3. Extract the archive (as the user to start IHS) to create an IHS/ subdirectory.
      4. Choose a final installation directory, such as /opt/IBM/IHS. Move the unpacked IHS/ subdirectory to the final installation path.
        mkdir -p /opt/IBM && mv IHS/ /opt/IBM/IHS
      5. Change your working directory to the final installation path.
        cd /opt/IBM/IHS
    2. Run the provided postinstall.{sh|bat} command with no parameters. If you want to distribute the binary files to multiple systems, do not run postinstall.{sh|bat} until the files are transferred.
    3. To emulate the swinging profiles of WebSphere Application Server, run postinstall.{sh|bat} from the symlink directory, as it stores the working directory in self-referential paths within several files.
    4. [Windows]Create a system service for the IBM HTTP Server installation.

      An example follows:

      bin\httpd.exe -k install -n IHS9A
    5. The installation is complete.
  2. Apply maintenance.
    1. Extract the archive from the stopped servers installation root.
    2. [Windows]Manually run the postinstall.bat script after each service is applied.

    All service fixes for the IBM HTTP Server archive installation are in the cumulative maintenance. Individual interim fixes are not available.

  3. Uninstall IBM HTTP Server.
    1. Stop the server. If the IBM HTTP Server Administration Server was enabled, stop it, also.
    2. [AIX]Run the slibclean command as root.
    3. Remove the installation directory.
    4. [Windows]Run services.msc to remove any system services.
    Results: You can now configure your server for Liberty or WebSphere Application Server.