Setting up Version 5.x and Version 6.0.x coexistence

You can install a Version 6.0.x product to coexist with another installation instance of Version 5.x.

Before you begin

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

About this task

Each installation of the base product is a standalone application server (server1) with its own set of unique configuration files.

Each installation of the Network Deployment product can be a standalone deployment manager (dmgr) with its own set of unique configuration files for its cell, a managed node, or a standalone application server.

Be aware of multiple instance limitations, between:
  • 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 9060 in Version 6.0.x (9090 in Version 5.x) as the administrative console port and port 9043 as the administrative console secure port by default. You should not run both the deployment manager and the WebSphere 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.

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 Version 5.x Network Deployment and the Version 6.0.x product on the same machine.
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 is displayed 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.

Use the following procedure to install multiple installation instances.

Procedure

  1. Use the Installation wizard to install another installation. If you intend to share a single Web server among installations, 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.
  2. Share a Web server among multiple installation instances.
    1. Use the Plug-in Installation wizard to select a Web server plug-in.
    2. Use the administrative console to generate the plug-in configuration files for every installation instance and to then merge them into one master configuration.
    3. Use the administrative console to replace the original plugin-cfg.xml file with the master file on the Web server.
    You can access samples from only one of the installation instances.
  3. 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.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 9:31:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tins_coexist3
File name: tins_coexist3.html