You can install WebSphere Application Server Version 6.1 to coexist with another installation instance of Version 5.x.
Each installation of the base product is a standalone application server with its own set of unique configuration files.
When you install any product a second time, the last installation is the one that is displayed in the registry.
Suppose you have installed three instances of the base WebSphere Application Server 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 WebSphere Application Server product instance.
If you intend to share a single Web server among installations, install the appropriate Version 6.1 Web server plug-in using the standalone Web server Plug-in installation wizard that is provided on the WebSphere Application Server product disk.
See Port number settings in WebSphere Application Server versions.
If you create a Version 6.1 managed node on the same system where another Version 6.1 managed node exists, the addNode command increments the port assignments of the second node agent process so that no conflict occurs. The Profile Management tool also handles the port assignments successfully when you federate a custom node during the creation of the custom profile.
Contrast the Version 6.1 coexistence scenario just described to the following cross-version scenario where a Version 5.x or 6.0.x managed node exists.
Assume that you create a Version 6.1 managed node on the same system where a Version 5.x or 6.0.x managed node exists. Neither the addNode command nor the Profile Management tool has a record of the Version 5.x or 6.0.x port assignments. Port assignments on the second, Version 6.1 node agent process are not incremented. Conflicts occur.
The conflicts prevent the second node from starting. If you start the Version 5.x or 6.0.x node first, the Version 6.1 node cannot start. If you start the Version 6.1 node first, the Version 5.x or 6.0.x node cannot start.
Perform the following procedure to create a Version 6.1 managed node with nonconflicting ports.
Do not federate the custom node as you create the custom profile. Select the check box on the Profile Management tool panel to federate the node later.
Use the netstat -a command to check existing port assignments. Analyze the port assignments to determine 12 sequential free ports.
This procedure assumes that no port assignments exist between 3320 and 3380.
Assume that you create an application server profile named V61MngNode in the default installation root directory on a Linux system.
cd /opt/IBM/WebSphere/AppServer/profiles/V61MngdNode/bin
./addNode.sh nittany.ibm.raleigh.com \ -conntype RMI 8879 \ -includeapps \ -user lions44 \ -password PSU -startingport 3333
The \ character is a continuation character for using more than one line to submit commands.
The -startingport parameter supplies the base port number for all node agent ports and increments all of the port values from the starting point. The nonconflicting port assignments let the new node agent run when the Version 5.x or 6.0.x node agent process is already running.
This procedure results in the ability to start your Version 5.x or 6.0.x node at the same time as your Version 6.1 node. The node agents can run on the same server.
WC_defaulthost 9081 WC_adminhost 9062 WC_defaulthost_secure 9444 WC_adminhost_secure 9045 BOOTSTRAP_ADDRESS 2810 SOAP_CONNECTOR_ADDRESS 8881 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS 9901 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS 9201 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS 9102 ORB_LISTENER_ADDRESS 9900 CELL_DISCOVERY_ADDRESS 7272 DCS_UNICAST_ADDRESS 9354
After migrating a Version 5.x or 6.0.x deployment manager to a Version 6.1 deployment manager, you can migrate the Version 5.x or 6.0.x managed nodes incrementally. See Migrating to a Version 6.1 managed application server for more information.