WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Setting up Version 4.0.x and Version 6 coexistence

Before you begin

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

Why and when to perform this task

You can install WebSphere Application Server Version 4.0.x and Version 6 on the same node. Change the ports to avoid conflicts during profile creation (see Using the Profile creation wizard for more information on profile creation).

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

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

Steps for this task

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

    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 topic 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 theNodeName
      

      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 installation wizard will display the default set of coexistence port numbers during profile creation time. 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 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. Communicating with Web servers describes how to configure this file for Version 6..
    • 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 Version 6 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. Replace the original plugin-cfg.xml file of the Version 5 installation with the master file.
  4. Fix any problems with environmental variables on Windows platforms. For example, installing WebSphere Application Server, Version 6 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.



Related tasks
Setting up Version 5 and Version 6 coexistence
Setting up Version 6 coexistence

Related reference
Port number settings in WebSphere Application Server versions
Installation: Resources for learning

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tins_coexist2.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)