Instant Messaging HA Overview (Sun Java System Communications Services 2005Q4 Release Notes)

Sun Java System Communications Services 2005Q4 Release Notes

Instant Messaging HA Overview

You use Sun Cluster with Instant Messaging to create a highly available deployment. This section provides information about HA requirements, terms used in examples in this chapter, and permissions you need to configure HA in the following sections:

Before you begin, you should be familiar with general HA concepts, and Sun Cluster software in particular. For more information, see HA Related Documentation.

HA Configuration Software Requirements

An Instant Messaging HA configuration requires the software shown in Table 3–7.

Table 3–7 Software Requirements for Instant Messaging HA Configuration


Software and Version	Notes and Patches
Solaris 9 OS SPARC Platform only	All versions of Solaris 9 OS are supported. Solaris 9 OS requires Sun Cluster 3.0 U3 or later. Solaris 9 OS includes Solaris Logical Volume Manager (LVM).
Solaris 8 OS SPARC Platform only	Solaris 8 Maintenance Update 7 (MU7) OS or later plus required patches.
Sun Cluster 3.1	Sun Cluster software must be installed and configured on all nodes in the cluster. To install Sun Cluster 3.1, use the Java Enterprise System installer by following the installation process in the Sun Java Enterprise System 2005Q4 Installation Guide. After you install the Sun Cluster software, you must configure the cluster. For information, refer to the Sun Cluster System Administration Guide for Solaris OS. For related documentation, see HA Related Documentation. Sun Cluster Patches For Solaris 8 and 9, you can download patches from SunSolve Online.
Solstice DiskSuite 4.x	Solstice DiskSuite is available for Solaris 8 OS only. Solstice DiskSuite is not required for Solaris 9 OS, which includes the Logical Volume Manager (LVM).
Veritas Volume Manager (VxVM) 3.x	Solaris 8 OS requires version 3.2 or later plus required patches. Solaris 9 OS requires version 3.5 or later plus required patches.
Veritas File System (VxFS) 3.x	Solaris 8 OS requires version 3.4 or later plus required patches. Solaris 9 OS requires version 3.5 or later plus required patches. HAStoragePlus requires patch 110435-08 or later.

HA Configuration Permission Requirements

To install and configure an Instant Messaging HA configuration, log in as or become superuser (root) and specify a console or window for viewing messages sent to /dev/console.

HA Configuration Terms and Checklist

Table 3–8 describes the variable terms used in the examples in this chapter for configuration examples. In addition, you will need to gather the information before you configure HA for Instant Messaging. You will be prompted for this information during configuration. Use this checklist in conjunction with the checklist in Chapter 1 of the Sun Java System Instant Messaging 7 2005Q1 Administration Guide.

Table 3–8 HA Configuration Checklist


Name in Example	Description	Your Value
`/global/im`	Global file system mount point used with a cluster file system or HAStoragePlus.
`/local/im`	Local directory to use as a mount point for the shared disk if you are using HAStoragePlus.
`im_logical_host`	Logical host name
`im_logical_host_ip`	Logical host IP numeric address
`im_node_1`	Node 1 FQDN
`im_node_2`	Node 2 FQDN
`im_resource_group`	Instant Messaging resource group.
`im_resource_group_store`	Instant Messaging storage resource.
`im_resource`	Instant Messaging resource.
`im_runtime_base` (Includes `im_runtime_base/db` and `im_runtime_base/logs`)	For the location of the runtime directory (which includes the database and log subdirectories), select global, shared partitions. For example: Instant Messaging runtime directory (`im_runtime_base`) `/global/im/var/opt/SUNWiim/default` on Solaris. Database subdirectory (`im_db_base`): `/global/im/var/opt/SUNWiim/default/db` Log subdirectory: `/global/ im/var/opt/SUNWiim/default/logs` See the Sun Java System Instant Messaging 7 2005Q1 Administration Guide for more information about the runtime directory and the database and logs subdirectories.