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.
Procedure
- 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.
- 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.
- Associate a Web server with each WebSphere Application Server.
- Use a separate Web server for each WebSphere Application Server.
- Create a Web server instance using the Web server documentation.
- 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. Communicating with Web servers
describes
how to configure this file for Version 6.0.x.
- 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.
- 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.
- 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.
This is described in the Installing IBM HTTP Server
article.
- Replace the original plugin-cfg.xml file
of the Version 5.x installation with the master file.
- 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.