You can migrate a Web server from supporting an earlier version of WebSphere Application Server to support the current version.
Steps for this task
Install the HTTP Server and its plug-in on a different machine with the following procedure:
Run the appropriate installation script for your platform:
This script installs the plug-in that you need and makes the necessary configuration changes for the supported Web server.
IBM HTTP Server Version 6.0 can coexist with earlier versions, or you can upgrade earlier versions to Version 6.0. Upgrading relieves you from having to uninstall and reinstall the HTTP server. Install Version 6.0 into the same directory structure as the earlier version to upgrade that version. If you install the HTTP Server into a different directory, Version 6.0 coexists with the previous version. By default, the administration server and the Web Server use the same ports as the previous version, which causes a conflict. However, you can change the port assignments on the port assignment panel of the WebSphere Application Server Installation wizard or the Profile creation wizard. See Installing the product and additional software.
Versions 4.0.x, 5.x, and 6.0.x of WebSphere Application Server use the same HTTP transport plug-in binary module. If the Web server configuration file contains WebSphere Application Server Version 4.0.x or 5.x plug-in information, you must manually remove it. Otherwise, when the HTTP Server attempts to start the second Version 6.0.x plug-in binary module, there is an error. The error indicates that the module is already loaded.
Version 4.0.x installations: Alias /IBMWebAS/ "C:\WebSphere\AppServer40\web\" Alias /WSsamples "C:\WebSphere\AppServer40\WSsamples\" Version 5.x installation: Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples" Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\" Version 6.0.x installation: Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples" Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\"
Starting with WebSphere Application Server Version 6.0, the following are true:
Use the following steps to generate a Web server plug-in configuration file that is based on topology. This method was used for generated plug-in configuration files in previous releases.
See GenPluginCfg command.
You should migrate to the application-centric approach that uses the Plug-ins installation wizard. The Plug-ins installation wizard generates scripts that can be used to create the Web server definition for that Web server and to map all of the applications that are currently deployed to the newly created Web server definition.
What to do next
The plug-in configuration file (plugin-cfg.xml) generated after successful migration from Version 5.x to Version 6.x is topology centric—that is, it includes all the applications within a cell. You cannot manage this cell-wide plug-in configuration file from the Version 6.x administrative console. It can be managed using the GenPluginCfg command or by using the Plug-in Config Generator MBean. See GenPluginCfg command.
Be aware that regenerating the plug-in configuration can overwrite manual configuration changes that you might want to preserve.
The application-centric generation of the plugin-cfg.xml file is supported using the Version 6.x administrative console. Being application centric means that the plugin-cfg.xml file generated in the administration console has a granularity that allows each application to be mapped to its specific Web or application server.
See Setting up a local Web server or Setting up a remote Web server.
See Communicating with Web servers and Web server plug-in configuration properties.
See Communicating with Web servers and Web server plug-in configuration properties.
Related concepts
Overview of migration and coexistence
Related tasks
Installing IBM HTTP Server
Editing Web server configuration files
Web server plug-in properties settings
Configuring IBM HTTP Server for Secure Sockets Layer mutual authentication