Java Messaging Server(MS) 6.3 is now supported on Sun Cluster 3.2. The qualification of Java Messaging Server on SC3.2 has been completed on sparc and x86 platforms. Java Messaging Server(MS) is an Internet messaging server that provides support for several email protocols like IMAP, POP3.
The Sun Cluster High Availability agent for Messaging Sever makes the application highly available in Sun Cluster environment. The Sun Cluster agent provides methods to start, stop and monitor the Java Messaging server application. It constantly watches the watcher process of MS, under PMF (Process Monitoring Facility). If the watcher dies, it restarts/failsover the watcher. Since the watcher process is the single point of failure, it is made highly available.
Java Messaging Server 6.3 High Availability agent is now certified on Sun Cluster 3.2. What does this mean? Some of the most important Solaris features like ZFS(Zeta File System) support, Solaris 10 non-global zones are now available with MS 6.3 HA agent. These features are very attractive to Messaging Server customers, especially ISPs since internet messaging server demands effective space usage and 7x24 availability.
Now that we have non-global zone support for MS 6.3, we shall take a look at configuring MS 6.3 HA agent on Solaris 10 non-global zones.
Note: This is not a complete Java Messaging Server 6.3 installation/configuration. I have described below only the pre-configuration and post-configuration steps for running the agent in Solaris 10 non-global zones.
|An example HA MS configuration would look something like this:|
A two-node cluster say Node1 and Node2, with a sparse root zone Zone1 installed on Node1 and a whole root zone Zone2 installed on N2.
1. If the MS 6.3 is installed in the global zone, the packages (SUNWmsgsr and SUNWscims) would be inherited to the non-global zone. This would, essentially, mean the /opt directory where MS installation exists, will be inherited to the zone.
1. Install messaging server 6.3 Binaries on all the cluster nodes(here, Node1 and Node2). Refer for installation: http://docs.sun.com/app/docs/doc/819-7560
2. Install LDAP server 6.1 and make it HA.
3. Install the Messaging Server HA Agent Package, SUNWscims on all the Cluster Nodes.
4. Install and boot the non-global zones, Zone1 and Zone2.
5. Create and enable a failover resource group with Logical hostname and HASP resource for ZFS with non-global zones in the Nodelist.
ex: # clresourcegroup create -n Node1:Zone1, Node2:Zone2 mail-rg
# clreslogicalhostname create -g mail-rg -h loghost
#clresource create -g mail-rg -t SUNW.HAStoragePlus -p
Zpools =ms-zpool -p AffinityOn=TRUE
# clresourcegroup online mail-rg
6. Execute "Configure" script on one of the cluster nodes(say Node1 in this example).
7. Execute "useconfig" and "ha_ip_config" on all the secondary cluster nodes(Node2 in this example).
ex: Path to the scripts: /opt/SUNWmsgsr/sbin/useconfig and /opt/SUNWmsgsr/sbin/ha_ip_config
The following two sections describe the configuration of Java Messaging Server 6.3 in non-global zones:
1. Sparse root zone(Zone1):
2. Whole root zone(Zone2):
The following steps describe creating and enabling an Messaging Server resource and a few tests to demonstrate how Sun Cluster keeps the messaging server highly available.
1. Create MS resource:
ex: # clresource create -g mail-rg -t SUNW.ims -p IMS_serverroot=/opt/SUNWmsgsr -p
2. Enable MS resource:
ex: clresource enable mail-rs
3. "clresourcegroup status" would display the resource status online on one of the non-global zones.
4. Failover the MS resource to another zone node.
ex: clresourcegroup switch -n Node1:Zone1
5. Try killing the watcher process and observe watcher process getting restarted.
For more information on Installation and Configuration of Sun Cluster HA Messaging Server 6.3 agent, refer to http://www.sun.com/bigadmin/features/hub_articles/message_srvr_cluster.pdf
Sun Cluster Engineering