You can migrate a web server so that it supports the latest version of WebSphere® Application Server.
This topic is about configuration migration, such as migrating deployment managers and federated nodes in a network deployment environment. The Application Migration Toolkit for WebSphere Application Server provides support for migrating applications from previous versions of WebSphere Application Server to the latest product version. For information about migrating applications, read more about the Application Migration Toolkit.
sptcfgWhen 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 8.0 configuration to the configuration of a previous version of IBM HTTP Server.
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
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
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.
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 8.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.
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 8.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 8.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 8.0 entries:
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.
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 then the IBM HTTP Server 8.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.
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.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |