Your data service configuration might not be supported if you do not observe these restrictions.
Consider the restrictions in this section to plan the installation and configuration of Sun Cluster HA for WebSphere MQ Integrator . This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for WebSphere MQ Integrator only.
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 only be configured 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 only be configured to run as a failover service.
Installing WebSphere MQ Integrator onto Cluster File Systems – Initially, the WebSphere MQ Integrator product is installed into /opt/mqsi and /var/mqsi.
/var/mqsi must be mounted 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, however 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 makes use of several directories within /var/mqsi, which needs to be available on all nodes within Sun Cluster as a Global File System. However, generated locks need to be located within a Local File System. Because of this, /var/mqsi/locks must be setup as a symbolic link to a Local File System.
It is considered best practice when mounting Global File Systems to mount them with the /global prefix and to mount Failover File Systems with the /local prefix. However, be aware that this is simply viewed as best practice.
The following example 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, ie local disk.
# 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 – Currently, the Sun Cluster HA for WebSphere MQ Integrator data service can only operate with a local RDBMS, ie 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, namely whenever the RDBMS restarts. However, this behavior is scheduled to be enhanced at a later date and also to include Sybase support.