|
Problem(Abstract) |
A common scenario for creating a cluster with two members
is to first have two base installations, each with an IBM® WebSphere®
Application Server (commonly server1). Many times each Application Server
has the necessary applications installed prior to running the addNode
command. After the addNode is run for the first node with the -includeApps
option, these applications are in the cell and cannot be added again when
the second node is added to the cell. At this point, you cannot create a
cluster and add the Application Server from each node to the cluster. |
|
|
|
Cause |
Use an existing Application Server as the first cluster
member. Use the default to form a new, blank cluster. After a cluster is
created, you can create new members (Application Servers), but existing
Application Servers cannot be added to the cluster. This means two
existing application servers cannot both be added to a cluster. |
|
|
Resolving the
problem |
To create a cluster, use the following steps:
- Run addNode with the -includeApps option for Node A.
- Run addNode without the -includeApps option for
Node B.
- If the Application Server that was added to the cell from Node B is
not needed, remove it from the configuration.
- Create a cluster, then select to create it with an existing server
using the Application Server from Node A as the existing server to add.
- Create a cluster member on Node B.
This results in a cluster with two members, each having the applications
from the original Application Server on Node A. Additional applications
can be installed directly into the cluster during the installation
process. |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|