[Version 5.0.2 and later]Coexistence support

Coexistence, as it applies to WebSphere Application Server products, is the ability of multiple installations of WebSphere Application Server to run on the same machine at the same time. Multiple installations include multiple versions and multiple instances of one version. Coexistence also implies various combinations of Web server interaction.

Version 5.x WebSphere Application Server products can coexist with the following supported versions. The installation wizard looks for these existing installations to determine if it should prompt for coexistence information:

All combinations of V3.5.x products, V4.x products, and V5.x products can coexist so long as there are no port conflicts. There are some coexistence limitations for V5 products that have the embedded messaging feature installed, as described later. These limitations are described as No EM in the following description.

[5.0 only]V3.5.5 and later products and V4.0.2 and later products can coexist with V5.x products:

Multiversion coexistence scenarios

Installed product V5.0.0 and V5.0.1 V5.0.2 and V5.1
Application Server Network Deployment Enterprise Application Server Network Deployment Enterprise V5.0.2
Standard Edition V3.5.5 and later Supported Supported Supported Supported Supported Supported
Advanced Edition V3.5.5 and later Supported Supported Supported Supported Supported Supported
Advanced Single Server Edition V4.0.2 and later Supported Supported Supported Supported Supported Supported
Advanced Edition V4.0.2 and later Supported Supported Supported Supported Supported Supported
Enterprise Edition V4.1 and later Supported Supported Supported Supported Supported Supported
WebSphere Application Server clients V4.0.x No EM No EM No EM No EM No EM No EM
WebSphere Application Server, V5.0.0 Supported Supported Supported No EM No EM No EM
Network Deployment V5.0.0 Supported Supported Supported No EM No EM No EM
Enterprise,V5.0.0 Supported Supported Supported No EM No EM No EM
WebSphere Application Server clients V5.0.0 Supported Supported Supported No EM No EM No EM
Application Server V5.0.1 Supported Supported Supported No EM No EM No EM
Network Deployment V5.0.1 Supported Supported Supported No EM No EM No EM
Enterprise V5.0.1 Supported Supported Supported No EM No EM No EM
WebSphere Application Server clients V5.0.1 Supported Supported Supported No EM No EM No EM
Application Server V5.0.2 No EM No EM No EM Supported Supported Supported
Network Deployment V5.0.2 No EM No EM No EM Supported Supported Supported
Enterprise V5.0.2 No EM No EM No EM Supported Supported Supported
WebSphere Application Server clients V5.0.2 No EM No EM No EM Supported Supported Supported
Application Server V5.1 No EM No EM No EM Supported Supported Supported
Network Deployment V5.1 No EM No EM No EM Supported Supported Supported
WebSphere Application Server clients V5.1 No EM No EM No EM Supported Supported Supported



[Version 5.0.2 and later]No EM: This status in the preceding tables describes an incompatibility between the embedded messaging features in different levels of Version 5. Version 5.0.0 and V5.0.1 support the embedded messaging feature at a service level less than CSD04, which is what V5.0.2 and V5.1 support. Because all V5 instances that coexist on a machine must use the same level of embedded messaging, there is a coexistence problem when two V5 instances use different levels of embedded messaging. If you want V5.0.0 to coexist with V5.1, for example, upgrade V5.0.0 to V5.0.2 by applying Fix Pack 2. See Upgrading a Version 5.0.0 or Version 5.0.1 product to Version 5.0.2.

[Version 5.0.2 and later]Each installation that includes embedded messaging should use a different node name. This is because the queue manager that is created for embedded messaging is named "WAS_node_server1". If the node name is already used by another installation with embedded messaging, the installer tries to create a queue manager that has the same name as a queue manager that already exists; this action will fail.

[Version 5.0.2 and later]When a second instance of WebSphere Application Server V5.0.x is installed on a host machine where embedded messaging is already installed, no additional MQ files are installed. The existing embedded MQ installation is used. However, during the second and subsequent V5.0.x installations with embedded messaging, a new queue manager and broker are created and configured for the new instance. For each instance, a createmq.node_server.log is created in the $WAS_HOME/logs directory. The contents of the log show if the embedded messaging components are configured correctly.

In addition to multiversion coexistence, WebSphere Application Server also lets you install multiple times on one machine (multiple installation instances), or install once and have multiple configurations (multiple configuration instances).

Multiple Version 5 instances on one machine include:

See Federating multiple Version 5 installation instances for information about mixed node cells, where a Version 5.1 deployment manager cell can include Version 5.0.x base nodes.


Related tasks
Federating multiple Version 5 installation instances
Setting up Version 3.5.x and Version 5 coexistence
Setting up Version 4.0.x and Version 5.x coexistence
Setting up Version 5 coexistence
Creating multiple Version 5 configuration instances



Searchable topic ID:   rins_coexist
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rins_coexist.html

Library | Support | Terms of Use | Feedback