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
Refer to the IBM WebSphere Application Server supported hardware, software, and APIs site for current requirements.
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.
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.
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.
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.x Samples and Version 6 Samples in the file, you can access only the Version 6 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.
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.
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