Migrate from previous releases of IBM HTTP Server

+

Search Tips   |   Advanced Search

 

Overview

If we are upgrading from a previous version of IBM HTTP Server and we want to install the new version in the same directory location, we must first uninstall the previous version of IBM HTTP Server.

Consider the following items when upgrading IBM HTTP Server.

 

Procedure

  1. Saving customized configuration files from our previous IBM HTTP Server installation.

    This is only necessary if you want to install the new version of IBM HTTP Server in the same directory location as the old version.

    1. Uninstall the previous IBM HTTP Server version. This will leave behind any customized configuration files added after the initial installation.

    2. Rename the directory containing the files of the uninstalled IBM HTTP Server

    3. Install the new IBM HTTP Server

    4. Overwrite the new IBM HTTP Server configuration files with the saved files from the renamed directory

  2. Upgrading from IBM HTTP Server V2.0. The configuration directives are compatible; however, on some platforms, the Application Programming Interface (API) for third-party modules has changed as follows:

    • IPv6 support is provided on HP-UX and Solaris platforms. Because of this change, third-party modules that use fields in the apr_sockaddr_info_t structure may need to be recompiled. Providers of such modules need to look at how the definition of apr_sockaddr_info_t varies when IPv6 is supported in order to determine if their module has to be recompiled.

  3. Upgrading from IBM HTTP Server V1.3. The main task of upgrading from IBM HTTP Server V1.3 is obtaining versions of third-party modules which are compatible with IBM HTTP Server V6.1 or Apache HTTP Server V2.0.

    Configuration changes will be required as well. These are described in the section "Run-time configuration changes"

    IBM HTTP Server modules retain the same configuration directives from IBM HTTP Server V1.3 to IBM HTTP Server V6.1, with the exception of Fast Response Cache Accelerator (FRCA). Using the Port directive to define the port number FRCA will listen on is replaced by the AfpaPort directive.

    The following features in IBM HTTP Server V1.3 are not available in IBM HTTP Server V6.1:

    • Disk caching proxy

    • Digest authentication

    • Simple Network Management Protocol (SNMP) agent

    • Windows performance monitor

    The new htdbm command is the preferred way to manipulate user ID databases when using mod_auth_dbm. The htdbm and mod_auth_dbm modules are consistent in the set of supported database formats. By default, the dbmmanage command may use a database format which is not supported by mod_auth_dbm.



 

Related tasks


Uninstall IBM HTTP Server