Configuration Restrictions

The configuration restrictions in the subsections that follow apply only to Sun Cluster HA for WebSphere MQ.

Your data service configuration might not be supported if you do not observe these restrictions.

Restriction for the supported configurations of Sun Cluster HA for WebSphere MQ

The Sun Cluster HA for WebSphere MQ data service can only be configured as a failover service.

Single or multiple instances of WebSphere MQ can be deployed in the cluster.

WebSphere MQ can be deployed in the global zone, whole root non-global zone or a whole root failover non-global zone. See Restriction for multiple WebSphere MQ instances for more information.

The Sun Cluster HA for WebSphere MQ data service supports different versions of WebSphere MQ, however you must check that the Sun Cluster HA for WebSphere MQ data service has been verified against that version.

Restriction for the Location of WebSphere MQ files

The WebSphere MQ files are where the queue manager data files /var/mqm/qmgr/queue-manager and /var/mqm/log/queue-manager are stored.

These WebSphere MQ files needs to be placed on shared storage as either a cluster file system or a highly available local file system.

Refer to Step 5 and Step 6 in How to Install and Configure WebSphere MQ for a more information.

Restriction for multiple WebSphere MQ instances

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

If you intend to deploy multiple WebSphere MQ instances with different versions you will need to consider deploying WebSphere MQ in separate whole root non-global zones.

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

Within these examples:

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

• Both nodes have two non-global zones each named z1 and z2.

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

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

Although these examples show non-global zones z1 and z2, you may also use global as the zone name or omit the zone entry within the Nodelist property value to use the global zone.

Example 1 Run multiple WebSphere MQ instances in the same failover resource group.

Create a single failover resource group that will contain all the WebSphere MQ instances in the same non-global zones across node1 and node2.

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

• + Only one non-global zone per node is required.

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

Example 2 Run multiple WebSphere MQ instances in separate failover resource groups.

Create multiple failover resource groups that will each contain one WebSphere MQ instance in the same non-global zones across node1 and node2.

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

• + Only one non-global zone per node is required.

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

Example 3 Run multiple WebSphere MQ instances within separate failover resource groups and zones.

Create multiple failover resource groups that will each contain one WebSphere MQ instance in separate non-global zones across node1 and node2.

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

• + Multiple WebSphere MQ instances have independent failover in separate failover resource groups and separate non-global zones.

• + All WebSphere MQ instances are isolated within their own separate non-global zones.

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

Example 4 Run multiple WebSphere MQ instances in separate failover resource groups that contain separate failover zones across node1 and node2.

Create multiple failover resource groups that will each contain a failover zone. Each failover zone can then contain one or more WebSphere MQ instances.

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

• + Multiple WebSphere MQ instances have independent failover within separate failover resource groups and separate failover zones.

• + The same failover zone per resource group is used per node.

• + Each failover zone is only active on one node at a time.

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

If your requirement is simply to make WebSphere MQ highly available you should consider choosing a global or non-global zone deployment over a failover zone deployment. Deploying WebSphere MQ within a failover zone will incur additional failover time to boot/halt the failover zone.