Determine which Solaris zone WebSphere MQ will use (Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS)

Sun Cluster Data Service for WebSphere MQ Guide for Solaris OS

Determine which Solaris zone WebSphere MQ will use

Solaris zones provides a means of creating virtualized operating system environments within an instance of the Solaris 10 OS. Solaris zones allow one or more applications to run in isolation from other activity on your system. For complete information about installing and configuring a Solaris Container, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

You must determine which Solaris zone WebSphere MQ will run in. WebSphere MQ can run within a global zone, non-global zone or in a failover zone configuration. Table 2 provides some reasons to help you decide.

Note –

WebSphere MQ can be deployed within the global zone, whole root non-global zone or whole root failover non-global zone, also referred to as a failover zone.

Table 2 Choosing the appropriate Solaris Zone for WebSphere MQ


Zone type	Reasons for choosing the appropriate Solaris Zone for WebSphere MQ
Global Zone	Only one instance of WebSphere MQ will be installed. Non-global zones are not required.
Non-global Zone	Several WebSphere MQ instances need to be consolidated and isolated from each other. Different versions of WebSphere MQ will be installed. Failover testing of WebSphere MQ between non-global zones on the same node is required.
Failover Zone	You require WebSphere MQ to run in the same zone regardless of which node the failover zone is running on.

Note –

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.