Restriction for multiple WebSphere Message Broker instances

The Sun Cluster HA for WebSphere Message Broker data service can support multiple WebSphere Message Broker instances, potentially with different versions.

If you intend to deploy multiple WebSphere Message Broker instances you will need to consider how you deploy WebSphere Message Broker in the global zone or whole root zones.

The purpose of the following discussion is to help you decide how to use the global zone or whole root zones to deploy multiple WebSphere Message Broker instances and then to determine what Nodelist entries are required.

The Nodelist entry is used when the resource group is defined using the clresourcegroup command. The Sun Cluster HA for WebSphere Message Broker must use the same resource group that is used for the WebSphere MQ and database resources.

You must therefore determine how the WebSphere Message Broker will be deployed in the cluster before the WebSphere MQ resource group is created so that you can specify the appropriate Nodelist entry.

Within these examples:

• There are two nodes within the cluster, node1 and node2.

• Both nodes have two zones named z1 and z2.

• Each example listed simply shows the required Nodelist property value, via the -n parameter, which is used when creating a failover resource group.

• Benefits and drawbacks are listed within each example as + and -.

Example 1 Run multiple WebSphere Message Broker instances in the global zone in one resource group.

Create a single failover resource group that will contain all the WebSphere Message Broker instances that will run in the global zones across node1 and node2.

# clresourcegroup create -n node1,node2 RG1

• + Only the global zone per node is required.

• - Multiple WebSphere Message Broker instances do not have independent failover as they are all within the same failover resource group.

• - Under normal operation, only one node of the cluster at any time is actively processing the WebSphere Message Broker workload.

Example 2 Run multiple WebSphere Message Broker instances in the global zone in separate resource groups.

Create multiple failover resource groups that will each contain one WebSphere Message Broker instance that will run in the global zones across node1 and node2.

# clresourcegroup create -n node1,node2 RG1
# clresourcegroup create -n node2,node1 RG2

• + Only the global zone per node is required.

• + Multiple WebSphere Message Broker instances have independent failover in separate failover resource groups.

• + Under normal operation, each node of the cluster is actively processing a WebSphere Message Broker workload, thereby utilizing each node of the cluster.

Example 3 Run multiple WebSphere Message Broker instances in zones in one resource group.

Create a single failover resource group that will contain all the WebSphere Message Broker instances that will run in the same zones across node1 and node2.

# clresourcegroup create -n node1:z1,node2:z1 RG1

• + Only one zone per node is required.

• - Although all zones are booted, only one zone at any time is actively processing the WebSphere Message Broker workload.

• - Multiple WebSphere Message Broker instances do not have independent failover as they are all within the same failover resource group.

• - Multiple WebSphere Message Broker instances are not isolated within their own separate zones.

Example 4 Run multiple WebSphere Message Broker instances in zones in separate resource groups.

Create multiple zones, where each zone pair will contain just one WebSphere Message Broker instance that will run in the same zones across node1 and node2.

# clresourcegroup create -n node1:z1,node2:z1 RG1
# clresourcegroup create -n node2:z2,node1:z2 RG2

• + Multiple WebSphere Message Broker instances have independent failover in separate failover resource groups and separate zones.

• + All WebSphere Message Broker instances are isolated within their own separate zones.

• - Each resource group requires a unique zone per node.