Setting up Version 4.0.x and Version 5.x coexistence

Before you begin

You must migrate prerequisite and corequisite programs to the levels required by WebSphere Application Server, Version 5. You must also identify ports in use in Version 4.0.1 before you begin the installation, to avoid possible conflicts during coexistence.

You can install WebSphere Application Server Version 4.0.1, with a minimum Service level of W401502, and Version 5 on the same node. IBM recommends that you keep the service level current.

Why and when to perform this task

By default, there are port conflicts between Version 4.0.1 and Version 5 that you must resolve. See Migrating from V4.0.1 for more information. The next step is to setup the Webserver to support V4.0.1 and V5 coexistence.

Steps for this task

  1. Associate a Web server with each WebSphere Application Server.
    • Use a separate Web server for each WebSphere Application Server.
      1. Create a Web server instance using the Web server documentation.
      2. Install the appropriate Web Server plug-in feature, and identify the Web server configuration file location. (For example, identify the location of the httpd.conf file for IBM HTTP Server.)
    • Use the same Web server for both WebSphere Application Server versions.

      To use the same Web server for both Application Server versions, you must first upgrade the Web server to the common level supported by both versions of the application server.

      Follow this procedure to use the same Web server for both WebSphere Application Server versions.

    1. Install the appropriate Web Server plug-in feature, and identify the Web server configuration file location. (For example, identify the location of the httpd.conf file for the IBM HTTP Server that is associated with Version 4.0.1.)
    2. Edit the Web server configuration file to remove entries for Version 4.0.1, as described in the Migrating plug-ins, one machine at a time (tins_websmig2) topic in the base Application Server information center.
      The WebSphere Application Server Version 5, or higher, plug-in acts as the routing agent to route requests to both versions.
    3. Generate the plug-in configuration files for both versions of the Application Server.
    4. Edit the Version 4.0.1 plugin-cfg.xml file and the Version 5 plugin-cfg.xml file, to merge their entries into a combined file of all Web context roots.
      Web context roots must be unique across Application Server versions. If there is a common context root across versions, requests are served by the plug-in instance that was last loaded.

      If you have both Version 4.0.1 Samples and Version 5 Samples in the file, you can access only the Version 5 Samples after merging the configuration files because there is one context root for Samples.

      This is described in the Preparing to install and configure a Web server (tins_webserver) topic in the base Application Server information center.

      Whenever you modify the plugin-cfg.xml file for either version, you must manually merge the files again, to make a master file.

      This is described in the Preparing to install and configure a Web server (tins_webserver) topic in the base Application Server information center.

      Whenever you modify the plugin-cfg.xml file for either version, you must manually merge the files again, to make a master file.

    5. Replace the original plugin-cfg.xml file of the Version 5 installation with the master file.

What to do next

Return to Migrating and coexisting to continue.

Related reference
Installation: Resources for learning



Searchable topic ID:   tins_coexist2
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tins_coexist2.html

Library | Support | Terms of Use | Feedback