... h1. Configuring Messaging Server for High Availability
For information about configuring Messaging Server 7.0 for high availability, see the following chapter in the _Messaging Server 6.3 Administration Guide_: [*Configuring High Availability*|http://docs.sun.com/app/docs/doc/819-4428/bgacf?a=view].
The link shown above provides the information you need to configure the Veritas Cluster Server or Sun Cluster high availability clustering software and prepare it for use with the Messaging Server.
{note:title=A Note About the Legacy Documentation}
Some information in the Messaging Server 6.3 documentation is out of date. The following sections describe information new in Messaging Server 7.0 which supersedes corresponding information in the _Messaging Server 6.3 Administration Guide_.
{note}
The remainder of this page contains the following topics:
{toc:minLevel=2|maxLevel=2}
h2. New Supported Versions of High-Availability Software in Messaging Server 7.0
Ignore section *3.1, Supported Versions*, in the _Messaging Server 6.3 Administration Guide_.
For the latest supported versions and platforms, see [High Availability Support|CommSuite6:Communications Suite 6 Component Products Release Notes#hasupport].
h2. New Installation Methods for Messaging Server 7.0
Ignore section *3.3.1, Cluster Agent Installation*, in the _Messaging Server 6.3 Administration Guide_.
Instead, use the following information:
A cluster agent is a Messaging Server program that runs under the cluster framework.
The Sun Cluster Messaging Server agent is installed when you select Messaging Server Sun Cluster HA Agent 7.0 through the Communications Suite installer.
# Run the Communications Suite installer command:\\
{noformat}
# commpkg install
{noformat}
When prompted, select the Messaging Server Sun Cluster HA Agent 7.0 software.\\
# Run the Sun Cluster HA Agent pre-configuration command: \\
{noformat}
# <ms_scha_base>/bin/init-config
{noformat}
h2. New Installation Paths for Messaging Server Sun Cluster HA Agent 7.0
Wherever you see references to the Messaging Server 6.3 _msg-svr-base_ path:
{noformat}
/opt/SUNWmsgsr/
{noformat}
use the Messaging Server 7.0 _msg-svr-base_ path instead:
For 32-bit Messaging Server 7.0:
{noformat}
/opt/sun/comms/messaging
{noformat}
For 64-bit Messaging Server 7.0:
{noformat}
/opt/sun/comms/messaging64
{noformat}
The Messaging Server Sun Cluster HA Agent 7.0 is by default now installed under
{noformat}
/opt/sun/comms/msg_scha
{noformat}
h2. Installing Messaging Server Sun Cluster HA Agent in Solaris Zones
Sun Cluster has added support for Solaris Zones. In this scenario, the Messaging Server Sun Cluster HA agent should be installed in the global zone (and automatically installed in non-global zones). The Comms Installer will do this for you as long as you do the install in the global zone.
Take the following steps to install the Messaging Server Sun Cluster HA agent in non-global zones:
# Run the Communications Suite installer command in the global zone only: \\
{noformat}
# commpkg install
{noformat}
When prompted, select the Messaging Server Sun Cluster HA Agent 7.0 software. This command installs the Messaging Server Sun Cluster HA Agent package on global zone and all non-global zones.\\
# Run the Sun Cluster HA Agent pre-configuration command in the global zone only: \\
{noformat}
# <ms_scha_base>/bin/init-config
{noformat}
h2. Using the {{useconfig}} Utility
The {{useconfig}} utility allows you to share a single configuration between multiple nodes in an HA environment. This utility is not meant to upgrade or update an existing configuration. Note that only {{useconfig}} command usage has been changed in this release. All the MS HA info from the previous release is still valid.
For example, if you are upgrading your first node, you will install through the Communications Suite Installer and then configure Messaging Server. You will then failover to the second node where you will install the Messaging Server package through the Communications Suite Installer, but you will not have to run the Initial Runtime Configuration Program (configure) again. Instead, you can use the useconfig utility.
|