Migrate Web server configurations

 

+

Search Tips   |   Advanced Search

 

 

Overview

This topic how to migrate a Web server from supporting...

IBM WebSphere Application Server, V4.0.x or V5.x

...to supporting...

IBM WAS Network Deployment, V6

 

Procedure

  1. Install the IBM HTTP Server, v6 and its plug-in, or a plug-in for another supported Web server from the product CD-ROM.

    Install the HTTP Server and its plug-in on a different machine with the following procedure:

    1. Insert the product CD-ROM labelled, WebSphere Application Server, IBM HTTP Server, into the machine.

    2. Close the launchpad if it starts automatically.

    3. Change directories to the IHS directory on the product CD-ROM.

    4. Click the installation script for your platform, to install the IBM HTTP Server:

      • InstallIHS.sh
      • InstallIHS.bat

      This script installs the plug-in we need and makes the necessary configuration changes for the supported Web server.

    IBM HTTP Server, v6 can coexist with earlier versions, or one can upgrade earlier versions to V6.0. Upgrading relieves you from having to uninstall and reinstall the HTTP server. Install V6.0 into the same directory structure as the earlier version to upgrade that version. If you install the HTTP Server into a different directory, V6.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, one can change the port assignments on the port assignment panel of the WebSphere Application Server installation wizard or the Profile creation wizard.

    • Change the port number assignments for the new installation if you install into a separate directory. We can change port numbers on the coexistence panel. We can back track through the installation wizard and change the port settings if you have not already done so. Or, one can change the port settings after installation, in the httpd.conf file in the HTTP Server directory.

    • Update the IBM HTTP Server httpd.conf configuration entries to remove entries for earlier WAS versions if you install into the same directory as an earlier version.

      Versions 4.0.x, 5.x, and 6 of WAS use the same HTTP transport plug-in binary module. If the Web server configuration file contains WAS V4.0.x or V5.x plug-in information, manually remove it. Otherwise, when the HTTP Server attempts to start the second V6 plug-in binary module, there is an error. The error indicates that the module is already loaded.

      The configuration file might contain duplicate entries for accessing WAS Samples. Remove any aliases for previous versions and retain the V6 entries 

      V4.0.x installations:
Alias /IBMWebAS/  "C:\WebSphere\AppServer40\web\"
Alias /WSsamples  "C:\WebSphere\AppServer40\WSsamples\"

V5 installation:
Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples"
Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\"

V6 installation:
Alias /WSsamples "c:\Program Files\WebSphere\AppServer\WSsamples"
Alias /IBMWebAS/ "c:\Program Files\WebSphere\AppServer\web\"

  2. Migrate plug-ins to work with IBM WebSphere Application Server, V6. Starting with WAS V6.0:

    • Web servers can be represented in the administrative console.

    • The Web server plug-in configuration file (plugin-cfg.xml) is associated with every Web server definition instead of one cell-wide plug-in configuration file.

    • The settings in the generated plug-in configuration file are based on the list of applications that are deployed on the hosting Web server.

    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.

    1. Use the GenPluginCfg.bat or GenPluginCfg.sh script to generate the plug-in configuration file.

    2. Manually propagate the generated plug-in configuration file from the machine on which the WAS resides to the remote Web server.

    3. Use the Plug-ins installation wizard to configure the Web server. Instead of using the default plug-in configuration file location, specify the new location of the plug-in configuration file that was propagated in the previous step.

    It is recommended that you migrate to the application-centric approach which 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.

 

Result

You now understand what do to install or migrate a Web server and plug-in to work with WebSphere Application Server, including installing the Web server on the same machine with the Application Server, or on different machines.

 

What to do next

After migrating your Web server, install the WebSphere Application Server product or migrate a previous installation:

 

See Also

Migration and coexistence overview

 

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