Sun Cluster Data Service for WebSphere Message Broker Guide for Solaris OS

Configuration Requirements

The configuration requirements in this section apply only to Sun Cluster HA for WebSphere Message Broker.

Caution – Caution –

If your data service configuration does not conform to these requirements, the data service configuration might not be supported.

Determine which Solaris zone WebSphere Message Broker 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 Message Broker will run in. WebSphere Message Broker can run within a global zone or zone configuration. Table 3 provides some reasons to help you decide which zone is appropriate.

Table 3 Choosing the appropriate Solaris zone for WebSphere Message Broker

Zone type 

Reasons for choosing the appropriate Solaris Zone for WebSphere Message Broker 

Global Zone 

Only one instance of WebSphere Message Broker will be installed. 

You are upgrading your cluster where previously a single or multiple WebSphere Message Broker instances were deployed on the cluster nodes. 

Zones are not required. 

Non-global Zone 

Multiple WebSphere Message Broker instances need to be consolidated and isolated from each other. 

Different versions of WebSphere Message Broker will be installed. 

Failover testing of WebSphere Message Broker between zones on a single node cluster is required.