Set up Version 4.0.x and Version 5 coexistence

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

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

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

1. Migrate prerequisite and corequisite programs to the levels required by WAS, Version 5.

   Refer to the IBM WebSphere Application Server supported hardware, software, and APIs
   http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html site for current requirements.

2. Resolve port conflicts.

   Refer to the Port number settings in WAS versions topic to see a list of default port numbers, and where they are defined.

   Inspect the configuration of the previous version...

   • For WAS Advanced Single Server Edition, Version 4.0.x: Inspect the server-cfg.xml file to get port values for the configuration.

   • For WAS 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 installation wizard displays a default set of coexistence port numbers as suggested Version 5 port numbers. Change the values to ports that are not in use. The installation wizard uses whatever values you approve.

     Change conflicting HTTP transport ports manually, if necessary.

3. Associate a Web server with each WAS.

   • Use a separate Web server for each WAS.

     1. Create a Web server instance using the Web server documentation.

     2. Select the appropriate Web Server plug-in feature during WAS installation, 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 WAS versions.

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

     Follow this procedure to use the same Web server for both WAS versions.

   1. Select the appropriate Web Server plug-in feature during WAS installation, 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.x.) the Web server configuration file to remove entries for Version 4.0.x. The WAS, Version 5 plug-in acts as the routing agent to route requests to both versions.

   2. Generate the plug-in configuration files for both versions of the Application Server.

   3. 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 5 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.

 

See Also

Setting up Version 5 coexistence
Port number settings in WAS versions
Installation: Resources for learning

 

---