Setting up V5 coexistence

This task describes how to install a product to coexist with another installation instance of V5.0.x.

 

Overview

After installing the WebSphere Application Server product, you can install it again on the same machine.

 

Overview

Select the new installation option from the installation wizard panel, to install a new instance instead of adding features to the last installation, and to install into a separate installation directory. Select the coexistence option to provide nonconflicting ports.

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 is a stand-alone deployment manager (dmgr) with its own set of unique configuration files for its cell.

Be aware of multiple instance limitations, between:

• Incompatible service levels of the embedded messaging feature.

  If you attempt to install V5.0.2 or V5.1 when V5.0.0 or V5.0.1 with the embedded messaging feature is already on the machine, you cannot select the embedded messaging feature. An incompatibility exists between the service level versions of embedded messaging. The level of embedded messaging for V5.0.0 and V5.0.1 differs from the level supported on V5.0.2 and V5.1. Upgrade the V5.0.0 or V5.0.1 node to V5.0.2 before installing another instance of V5.0.2 or V5.1.

• The base WebSphere Application Server 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 9090 as the administrative console port and port 9043 as the administrative console secure port by default. It is not recommended that you 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 WebSphere Application Server 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.

• The base WebSphere Application Server product and another installation of the base WebSphere Application Server product, or the Network Deployment product and another installation of the Network Deployment product.

  You can install another instance of either product, by selecting to do so at the prompt, and by changing the installation directory.

  The most recent installation is the only one in the operating system registry.

  If you install more than two total instances of either product (more than one of each, or two of either and none of the other), the third and subsequent installations require that you change all port numbers on the coexistence panel to avoid potential conflicts.

  To uninstall a product instance, always use the operating system remove program function, such as the Add/Remove program on Windows platforms. To uninstall an unregistered instance, use the Uninstall.exe or uninstall command in the _uninstall directory of the install_root that matches the instance you intend to remove.

Reasons to use multiple installation instances include:

• You can achieve complete isolation between each WebSphere Application Server instance. You can uninstall one instance independently of the others.

• You can federate each installation instance of the base WebSphere Application Server product to a deployment manager cell.

• You can install the base WebSphere Application Server more than once on the same machine.

• You can install Network Deployment more than once on the same machine.

• You can install V5.0.x Network Deployment and the V5.1 product on the same machine. There are some limitations involving the embedded messaging feature. The level of embedded messaging for V5.0.0 and V5.0.1 differs from the level supported on V5.0.2 and V5.1.

Reasons to not use multiple installation instances include:

• The machine might have a hard disk space constraint.

• You can use the operating system registry to locate the last installed instance of a WebSphere Application Server 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 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.

The Creating multiple V5 configuration instances topic describes installing the base WebSphere Application Server product or the Network Deployment product once and creating multiple configuration instances.

Use the following procedure to install multiple installation instances.

 

Steps for this task

1. Upgrade V5.0.0 or V5.0.1 with embedded messaging to V5.0.2.

2. Use the installation wizard to install another installation.

   If you intend to share a single Web server among installations, install a Web server plug-in feature during one installation only, as described in the next step.

3. Share a Web server among multiple installation instances.

   1. Select a Web server plug-in feature during one installation only.

   2. Generate the plug-in configuration files for every installation instance.

   3. Edit the plugin-cfg.xml configuration files to merge them into one master configuration.

   4. Replace the original plugin-cfg.xml file with the master file on the Application Server where you selected the Web server plug-in feature.

   You can access samples from only one of the installation instances.

4. Federate multiple installation instances into a deployment manager cell.

5. Create additional servers in a multiple instance or coexistence environment.

6. 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.

---

Creating servers in coexistence or multiple instance environments
Changing HTTP transport ports
Creating multiple V5 configuration instances

Port number settings in WebSphere Application Server versions

---

Searchable topic ID:   tins_coexist3

 

---