Previous Topic: Upgrade on a JBoss Cluster

Next Topic: Upgrade or Migrate the Identity Manager Server on a JBoss Cluster

Example: Identity Manager Server on a JBoss Cluster

CA Identity Manager uses the farming method of a JBoss cluster. In this type of cluster, you create a master node and it is usually the node that starts first in the cluster. As other nodes start, they receive deployment files from the master node. If the master node fails, another node becomes the new master node.

The following figure shows the relationship between the nodes and cluster members. Each node contains one cluster member. Each member of the cluster has a unique Server Peer ID. The master node would be cluster member 1, assuming it was created first.

jboss_cluster

In this figure, the messaging database is a central store for cluster members to share messages and each node contains three components:

Identity Manager Server

Provides the core functionality of the product.

JBoss Messaging Engine

Provides messaging functionality for members of the cluster using JMS.

Deployment Manager

Keeps track of the cluster members and the current master node member, which is also responsible for deploying files from the master node to other nodes.