Configuration Restrictions (Sun Cluster Data Service for WebSphere MQ Integrator Guide for Solaris OS)

Sun Cluster Data Service for WebSphere MQ Integrator Guide for Solaris OS

Configuration Restrictions

This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for WebSphere MQ Integrator only.

Caution –

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

For restrictions that apply to all data services, see the Sun Cluster Release Notes.

The Sun Cluster HA for WebSphere MQ Integrator data service can be configured only as a failover service – WebSphere MQ Integrator cannot operate as a scalable service and therefore, the Sun Cluster HA for WebSphere MQ Integrator data service can be configured only to run as a failover service.
Installing WebSphere MQ Integrator onto Cluster File Systems – Initially, you install the WebSphere MQ Integrator product into /opt/mqs and /var/mqsi.

You must mount /var/mqsi as a Global File System with a symbolic link for /var/mqsi/locks to a Local File System. It is recommended that /opt/mqsi be on a local disk. For a discussion of the advantages and disadvantages of installing the software on local versus cluster file system, see “Determining the Location of the Application Binaries” on page 3 of the Sun Cluster Data Services Installation and Configuration Guide

Mount /var/mqsi as a Global File System – WebSphere MQ Integrator uses several directories within /var/mqsi, which needs to be available on all nodes within Sun Cluster as a Global File System. Generated locks must be located within a Local File System. Because of this, you must setup /var/mqsi/locks as a symbolic link to a Local File System.

Note –

It is best practice to mount Global File Systems with the /global prefix and to mount Failover File Systems with the /local prefix.

Example 1–1 shows WebSphere MQ Integrator with /var/mqsi mounted as a Global File System through a symbolic link to /global/mqsi, with /var/mqsi/locks setup as a symbolic link to /var/mqsi_locks on the root file system, that is, local disk.

Example 1–1 WebSphere MQ Integrator with /var/mqsi/locks symbolically linked to a local file system

# ls -l /var/mqsi
lrwxrwxrwx   1 root     other         12 Sep  5 15:32 /var/mqsi ->
 /global/mqsi
#
# ls -l /global/mqsi/locks
lrwxrwxrwx   1 root     other         15 Sep 18 15:37 /global/mqsi/locks ->
 /var/mqsi_locks
#
# df -k /global/mqsi/locks
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c0t0d0s0    12731708 5792269 6812122    46%    / 
#
# more /etc/vfstab (Subset of the output)
/dev/md/dg_d6/dsk/d60   /dev/md/dg_d6/rdsk/d60  /global/mqsi
            ufs     4       yes     logging,global

The Sun Cluster HA for WebSphere MQ Integrator RDBMS – The Sun Cluster HA for WebSphere MQ Integrator data service can operate only with a local RDBMS, i.e. not a remote RDBMS and more specifically, only with DB2 and Oracle.

This restriction is because the Sun Cluster HA for WebSphere MQ Integrator data service needs to manage the restart scenarios for WebSphere MQ Integrator, whenever the RDBMS restarts.