This section provides information about upgrading from a previous
version of IBM HTTP Server.
Before you begin
If you are upgrading from a previous version of IBM HTTP Server and
you want to install the new version in the same directory location, you must
first uninstall the previous version of IBM HTTP Server.
About this task
Consider the following information when upgrading your version
of IBM HTTP Server.
Procedure
- Upgrading IBM HTTP Server from your previous installation
When you upgrade IBM HTTP Server from a previous version, complete
these steps to install the new version in the same directory location as the
previous version. If the new version is installed in a different directory,
you do not need to complete these steps.
- Uninstall the previous IBM HTTP Server version. This will leave behind
any customized configuration files added after the initial installation.
- Rename the directory containing the files of the uninstalled IBM HTTP
Server.
- Install the new IBM HTTP Server.
- Overwrite the new IBM HTTP Server configuration files with the saved files
from the renamed directory.
- 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.
- 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" at http://publib.boulder.ibm.com/httpserv/manual60/upgrading.html.
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.