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

You can install WebSphere Application Server Version 4.0.x and Version 6.0.x on the same node. Change the ports to avoid conflicts during profile creation.

Before you begin

You must migrate prerequisite and corequisite programs to the levels required by WebSphere Application Server, Version 6.0.x. You must also identify ports in use in Version 4.0.x before you begin the Version 6.0.x installation, to avoid possible conflicts during coexistence. The first two steps in this task describe these activities.

About this task

Silent installation also supports configuring for coexistence silently. You can specify nonconflicting port assignments in the pct options response file.

By default, there are port conflicts between Version 4.0.x and Version 6.0.x that you must resolve. Also, if you migrate more than two Version 4.0.x nodes to Version 6.0.x, there are port conflicts that you must resolve, as described in the Setting up Version 6.0.x coexistence article.

Procedure

  1. Migrate prerequisite and corequisite programs to the levels required by WebSphere Application Server Version 6.0.x.

    Refer to the IBM WebSphere Application Server supported hardware, software, and APIs site for current requirements.

  2. Resolve port conflicts.

    Refer to the Port number settings in WebSphere Application Server versions article to see a list of default port numbers, and where they are defined.

    Inspect the configuration of the previous version:
    • For WebSphere Application Server Advanced Single Server Edition Version 4.0.x: Inspect the server-cfg.xml file to get port values for the configuration.
    • For WebSphere Application Server Advanced Edition Version 4.0.x: Inspect the admin.config file to get port values for the configuration. When the administrative server is running, use this command:
      xmlConfig -export config.xml -nodeName node_name
      

      Review the config.xml file to look for <node action="update" name="nodename"> to find the appropriate node and port number assignments in the file. The Version 6.0.x installation wizard will display the default set of coexistence port numbers during profile creation. Change the values to ports that are not in use. The installation wizard uses whatever values you approve.

  3. 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. Use the standalone Web server plug-in installation wizard to install the appropriate Version 6.0.x Web server plug-in. This wizard is provided on a separate CD from the WebSphere Application Server Installation CD. The Web server plug-in configuration file, plugin_cfg.xml, is now configurable using the administrative console.
    • Use the same Web server for both WebSphere Application Server versions.

      To use the same Web server for both WebSphere 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 Version 6.0.x Web server plug-in using the standalone Web server plug-in installation wizard that is provided on a separate CD from the WebSphere Application Server Installation CD.
    2. Edit the Version 4.0.x plugin-cfg.xml file and the Version 6.0.x plugin-cfg.xml file, to merge their entries into a combined file of all Web context roots. You can use the administrative console to configure the Version 6.0.x plugin-cfg.xml file.

      Web context roots must be unique across WebSphere 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.x samples and Version 6.0.x samples in the file, you can access only the Version 6.0.x samples after merging the configuration files because there is one context root for samples.

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

    3. Replace the original plugin-cfg.xml file of the Version 5.x installation with the master file.
  4. Fix any problems with environmental variables on Windows platforms. For example, installing WebSphere Application Server Version 6.0.x updates the system variable PATH, potentially affecting tools with the same name across installations. To run tools with conflicting names, alter the PATH environment variable in a command window and place the directory for the former installation before the directory for the latter installation. For example, PATH=E:\WebSphere\AppServer\40\bin;%PATH%. Then, invoke the tools from the bin directory.

What to do next

Return to Migrating from, or coexisting with a previous version to continue.



In this information ...


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.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tins_coexist2
File name: tins_coexist2.html