Set up V5 and V6 coexistence
This task describes how to install a V6 product to coexist with another installation instance of V5.x.
Each installation of the base product is a stand-alone Application Server (server1) with its own set of unique configuration files.
Each installation of the Network Deployment product can be a stand-alone deployment manager (dmgr) with its own set of unique configuration files for its cell, a managed node, or a stand-alone Application Server.
Be aware of multiple instance limitations, between:
- Base WAS product and the Network Deployment product.
The deployment manager and the Application Server have two port conflicts in the default configuration settings for both products. Each product is configured to use port 9060 in V6 (9090 in V5.x) as the administrative console port and port 9043 as the administrative console secure port by default.
Do not run both the deployment manager and the Application Server on the same production machine, unless you have a machine with the capacity to handle the cumulative requirements of both products. However, if you do so, select the coexistence option during installation to change these port settings. There are no other port conflicts if you install a total of two instances, one base WAS product and one Network Deployment product.
If you install more than two instances, the third and subsequent installations require that you change all port numbers on the coexistence panel, to avoid potential conflicts.
Reasons to use multiple installation instances include:
- We can achieve complete isolation between each WAS instance. We can uninstall one instance independently of the others.
- We can federate each installation instance of the base WAS product to a deployment manager cell.
- We can install the base WAS more than once on the same machine.
- We can install Network Deployment more than once on the same machine.
Reasons to not use multiple installation instances include:
- The machine might have a hard disk space constraint.
- Use the operating system registry to locate the last installed instance of a WAS product only.
When you install any product a second time, the last installation is the one that appears in the registry.
- Uninstalling the last instance removes any record of the product in the registry.
Suppose you have installed three instances of the base WAS product. You use the remove program function of the operating system to uninstall the registered third copy of the base product. A registry record no longer exists that indicates the existence of the other two installation instances. Other applications cannot use a query of the operating system registry to detect the presence of either base WAS product instance.
The Using the Profile creation wizard topic describes installing the base WebSphere Application Server product or the Network Deployment product once and creating multiple profiles.
Use the following procedure to install multiple installation instances.
Procedure
- Use the installation wizard to install another installation.
If you intend to share a single Web server among installations, install the appropriate Version 6 Web server plug-in using the standalone Web server plug-in installation wizard provided on a separate CD from the WAS Installation CD.
- Share a Web server among multiple installation instances.
- Use the Plug-in Installation wizard to select a Web server plug-in.
- Use the administrative console to generate the plug-in configuration files for every installation instance and to then merge them into one master configuration.
- Use the administrative console to replace the original plugin-cfg.xml file with the master file on the Web server.
We can access samples from only one of the installation instances.
- Change port assignments in configuration files if you have a node that you cannot start because of port conflicts.
What to do next
Return to Migrating and coexisting to continue.
See also
Avoiding port conflicts in coexisting V5 and V6 node agents
Related Tasks
Using the Profile creation wizard
See Also
Port number settings in WAS versions