Migrating web server configurations

You can migrate a web server so that it supports the latest version of WebSphere® Application Server.

1. Migrate web server configurations:

   When you upgrade IBM® HTTP Server (IHS) from a previous version, complete the following 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 Steps 1 - 4. Whether you need to complete the remaining steps depends on how similar you want to make the Version 9.0 configuration to the configuration of a previous version of IBM HTTP Server.

   1. Stop the IBM HTTP Server and the IBM HTTP Server administration server.
   2. Copy the existing installation directory to a new location.

      This action preserves your configuration, keys, and content.

      Issue the following command to copy the previous installation:

      

      cp -rp current_install_directory new_directory_name 

      

      xcopy current_install_directory new_directory_name /s /e /k /i 

   3. Uninstall the previous IBM HTTP Server version.
   4. Remove the previous installation directory.

      Because the uninstall leaves behind some files, such as modified and added files, fixpack files, and uninstall files, you must manually remove the previous installation directory to complete the uninstall process. If you had any uninstall issues, review and backup the uninstall log files in the http_server_install/logs/uninstall directory before proceeding.

      Issue the following command to remove the installation directory:

      

      rm -r  current_install_directory  

      

      rd /s current_install_directory

   5. Install IBM HTTP Server Version 9.0.

      If upgrading your existing version, install into the directory where the previous installation was located.

      If installing the new version alongside an existing version, install the new version into a different directory.

   6. Run the Plug-ins Configuration Tool, the pct tool, to configure your web server plug-ins. Refer to the Configuring a web server plug-in using the pct tool topic for information on running the pct tool.
   7. Restore any custom configurations that were made to your previous version of IBM HTTP Server and IBM HTTP Server administration server.
      • Identify your previous customizations.

        If you used the httpd.conf configuration files provided with the previous version of IBM HTTP Server as the starting point for your configuration files, compare the content of each configuration file, with its corresponding .default file, within the directory containing your previous IBM HTTP Server installation. For example, if you compare the content of the httpd.conf file with the httpd.conf.default file you should see any customization that were made to the httpd.conf file since the original installation. Then perform similar comparisons for the other configuration files.

        If you did not use the httpd.conf configuration files provided with the previous version of IBM HTTP Server as the starting point for your configuration files, you will need to perform a more manual analysis to determine your previous settings. In this situation you might want to compare the settings in the httpd.conf.default file provided with the new IBM HTTP Server, with the settings in the httpd.conf.default file provided with the previous IBM HTTP Server version. This comparison enables you to identify configuration differences in the two httpd.conf.default files. You can then use this information to modify your customized configuration file to work with the Version 9.0 IBM HTTP Server.

        Compare the bin/envars file to the bin/envars-std file within the directory containing your previous IBM HTTP Server installation. This identifies what customizations, if any that was made to this file.

      • Merge the customizations into the newly installed IBM HTTP Server configuration and envars files.

        After you identify the configuration customizations you made to your previous version of IBM HTTP Server, make these same changes, when applicable, to the configuration files for the Version 9.0 IBM HTTP Server.

        If the configuration files contain WebSphere Application Server plug-in statements from previous versions, remove them so as to not cause duplicates. If you do not remove these statements, when the HTTP Server attempts to start the Version 9.0 plug-in binary module, an error might occur that indicates that the module is already loaded.

        The configuration file might also contain duplicate entries for accessing WebSphere Application Server samples. Remove any aliases for previous versions and retain the Version 9.0 entries:

   8. Restore HTML content.
      If your web page content was previously stored under your IBM HTTP Server installation directory, copy those content files from the directory that contains your prior version of IBM HTTP Server into the installation directory for the new version.
   9. Copy any SSL KeyFiles, that might be within the installation directory of the previous IBM HTTP Server, into the new installation directory
2. Change port assignments for coexisting IBM HTTP Servers.

   If you installed the IBM HTTP Server into a new directory and retained your previous version of the IBM HTTP Server, by default the administration server and the Web Server use the same ports as the previous version administration server and Web Server. If you ever run both versions of the IBM HTTP Server simultaneously, port conflicts will occur unless you change the port numbers for one of the server versions.

   To modify the port numbers for one of the IBM HTTP Servers, edit the server configuration files for that IBM HTTP Server. These files are located in the http_server_install/conf directory.

3. Upgrade Apache plug-in modules.

   There are no Apache API changes from the previous major release so there should be no need to rebuild modules that worked with the previous release. However, if you use modules from third party vendors, then you should contact your vendors to verify they support the module with the version of IBM HTTP Server to which you are upgrading.

   Apache plug-in modules from sources other than the IBM HTTP Server Version 9.0 installation must be built to support Apache 2.2. The distributors of modules used with older versions of IBM HTTP Server might need to recompile the modules to support Apache 2.2.

   • WebSphere Application Server provides a plug-in for Apache 2.2 and IBM HTTP Server Version 9.0.
   • If you use modules from third party vendors, contact your vendor for a version of the module that works with the Apache 2.2 API (application programming interface).
   • If you use modules developed in-house, you must rebuild your modules to support Apache 2.2. The modules might also require some modifications.
4. Update the IHS service name.

   Update the IHS service name in the WebSphere Application Server web server definition if (1) this is a Windows server and (2) you installed IHS into the same directory where an earlier version was located, and (3) you are using a web server definition from that prior installation.

   For a IBM HTTP Server on a Windows server system, use 'Services' to determine the name used for the new IBM HTTP Server service, and then update the web server definition to use this service name.

5. Migrating web server definitions
   A web server definition is used to manage the web server from a stand alone profile or the deployment manager.

   Note:

   • If you have updated IBM HTTP Server on the same host and in the same directory, no action is required. The current web server definition will suffice.
   • If the updated IBM HTTP Server is on the original host but in a new directory, update the path by selected the web server:Servers > Server Types > Web Servers in the WebSphere Application Server administration console.
   • If the updated IBM HTTP Server is on a new host, follow the Plug-ins roadmap to create a new web server definition. You can remove the old web server definition when you have confirmed the new web server is working properly. See Selecting a web server topology diagram and roadmap for a full description.