There are two types of clusters:
Usually, a horizontal cluster is preferred. In a horizontal cluster, JVMs that reside on different physical machine are clustered. The obvious advantage to a horizontal cluster is that if one physical server goes down, the other physical server can continue to produce the applications in the JVM, resulting in high-availability. Also, from a systems engineer perspective, a horizontal cluster lets the engineer do work on one cluster member without bringing down the applications being produced by the JVMs in the cluster. For example, the engineer could bring down the server01 JVM, patch the server, restart the JVM, and bring it back up, without causing an outage, as the server02 JVM can still produce the application.
In a vertical cluster, JVMs that reside on the same physical machine are clustered. Similar to a horizontal cluster, a vertical cluster lets the engineer do work on one cluster member without bringing down every JVM. However, if the physical server goes down, the entire cluster also goes down.
Create new cluster with new JVMs.
- In the left panel of the WebSphere web console, expand Servers > Clusters, and select WebSphere application server clusters.
- Select New.
- At Step 1, enter the name of the cluster (such as cluster1) and select Next.
- At Step 2, give the member a name (such as server03), select the node, and select Next.
Note: You cannot add a JVM that already exists in the node. The creation of a member will create a new JVM.
- At Step 3, enter the name for the second member (such as server04), select the node, select Add Member, and select Next.
- Select Finish.
- Select Save.
Synchronize the node. You can then select the cluster and select start to start both JVMs (server03 and server04) in the cluster.
At Servers > Server types > WebSphere application servers, the servers in the cluster will be listed. In this example, server01 and server02 are not part of a cluster, and server03 and server04 are members of cluster1. This view also can be used to know if the JVMs are in a vertical or horizontal cluster. In this example, server03 and server04 are in a vertical cluster, as both are on the same physical server (was1).
Selecting the cluster and then expanding Cluster members allows you to see the members that are in the cluster.
Since web service applications do not have a UI and are not fronted by a web server, there isn’t a need for session and context replication between web services JVMs. These apps should be stateless, meaning an invocation of the app shouldn’t be dependent on data created/updated in session or context from a previous call. It may be reasonable to not cluster web services JVMs.