Configuring Instant Messaging for High Availability on the Solaris Platform

Configuring Instant Messaging for high availability (HA) provides monitoring and recovery from software and hardware failures. The high availability feature is implemented as a failover data service and not as a scalable service. This feature is supported only on the Solaris operating system. This chapter describes how to configure Instant Messaging for HA by using the Sun Cluster software. Before you begin, you should be familiar with the general HA concepts and the Sun Cluster software. For more information, see HA Related Documentation.

This chapter includes the following sections:

Instant Messaging HA Overview

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

HA Configuration Software Requirements

The Instant Messaging HA configuration requires the software as shown in the following table.

HA Configuration Permission Requirements

To install and configure an Instant Messaging HA configuration, log in or become superuser root and specify a console or window for viewing messages that exist in the /dev/console directory.

HA Configuration Terms and Checklist

The following table describes the variables 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 along with the configuration checklist described in Configuring Instant Messaging After Installation.

Setting Up HA for Instant Messaging

This section describes the steps necessary to set up high availability for Instant Messaging. This section contains the following topic:

Choosing a High Availability Model for Your Instant Messaging 8 Deployment

This section lists the high availability models, and describes the procedure to install and configure the asymmetric and symmetric models for deployment. This section contains the following topics:

The following table summarizes the advantages and disadvantages of each high availability model. Use this information to decide the appropriate model for your deployment.

High-Level Task List for an Asymmetric HA Deployment

The following is a list of the tasks necessary to install and configure Instant Messaging for asymmetric high availability:

1. Prepare the nodes.
   1. Install the Solaris operating system on all the nodes of the cluster.
   2. Install Sun Cluster software on all the nodes of the cluster.
   3. Install the Instant Messaging HA Agents package, SUNWiimsc, on all the nodes of the cluster by using the Communication Suite 6 Update 1 installer.
   4. Create a file system on the shared disk.
   5. Install Instant Messaging on all the nodes of the cluster by using the Communications Suite 6 Update 1 installer.
   6. Create a symbolic link from the Instant Messaging /etc/opt/SUNWiim directory to the shared disk IM_RUNTIME_DIR directory on all the nodes of the cluster.
2. Configuring the first or the primary node.
   1. Using the Sun Cluster command-line interface, set up HA on the primary node.
   2. Run the Instant Messaging configure utility on the primary node.
   3. Using the Sun Cluster command-line interface, create and enable a resource group for Instant Messaging.

For step-by-step instructions, see Installing and Configuring in an Asymmetric HA Environment.

High-Level Task List for a Symmetric HA Deployment

The following is a list of the tasks necessary to install and configure Instant Messaging for Symmetric High Availability:

1. Prepare the nodes.
   1. Install the Solaris operating system software on all the nodes of the cluster.
   2. Install the Sun Cluster software on all the nodes of the cluster.
   3. Create four file systems. You can create a cluster file systems or global file systems or failover file systems or local file systems.
   4. Create the necessary directories.
   5. Install the Instant Messaging HA Agents package, SUNWiimsc, on all nodes of the cluster by using the Communications Suit 6 installer.
2. Install and configure the first instance of Instant Messaging HA.
   1. Using the Communications Suite 6 installer, install Instant Messaging on the first node of the cluster.
   2. Using the Sun Cluster command-line interface, configure HA on the first node.
   3. Create a symbolic link from the Instant Messaging /etc/opt/SUNWiim directory to the shared disk IM_RUNTIME_DIR directory on the first node.
   4. Run the Instant Messaging configure utility on the first node.
   5. Using the Sun Cluster command-line interface, create and enable a resource group for Instant Messaging on the first node.
   6. Using the Sun Cluster command-line interface to test the successful creation of the resource group, perform a failover to the second node.
3. Install and configure the second instance of Instant Messaging HA.
   1. Using the Communications Suite 6 installer, install Instant Messaging on the second node of the cluster.
   2. Using the Sun Cluster command-line interface, configure HA on the second node.
   3. Create a symbolic link from the Instant Messaging /etc/opt/SUNWiim directory to the shared disk IM_RUNTIME_DIR directory on the secondary node.
   4. Run the Instant Messaging configure utility on the second node.
   5. Using the Sun Cluster command-line interface, create and enable a resource group for Instant Messaging on the second node.
   6. Using the Sun Cluster command-line interface to test the successful creation of the resource group, perform a failover to the first node.

For step-by-step instructions, see Installing and Configuring in a Symmetric HA Environment.

Installing and Configuring in an Asymmetric HA Environment

This section contains instructions for configuring an asymmetric high availability Instant Messaging cluster. This sections contains the following topics:

• Creating the File Systems for Your HA Deployment
• Creating the Instant Messaging Directory on All Shared Disks of the Cluster in Your HA Deployment
• Installing and Configuring HA for Instant Messaging 8

Creating File Systems for HA Deployment

Create a file system on the shared disk. The /etc/vfstab directory should be identical on all the nodes of the cluster.

For the cluster file system (CFS), the directory should be similar to the following example.

## Cluster File System/Global File System ##
/dev/md/penguin/dsk/d400 /dev/md/penguin/rdsk/d400 /global/im ufs 2 yes global,logging

For the failover file system (FFS), the directory should be similar to the following example.

## Fail Over File System/Local File System ##
/dev/md/penguin/dsk/d400 /dev/md/penguin/rdsk/d400 /local/im ufs 2 no logging

Note The fields in these commands are separated by tabs and not spaces.

Creating the Instant Messaging Directory on all the Shared Disks of the Cluster in the HA Deployment

For all the nodes of the cluster, create a directory, IM_RUNTIME_DIR, to store the configuration details and data. For example, to create an Instant Messaging directory on a shared disk, type either one of the following:
mkdir -p /local/im
or
mkdir -p /global/im

Installing and Configuring HA for Instant Messaging 8 Software

This section contains instructions for the tasks involved in installing and configuring HA for Instant Messaging. Perform the following tasks to complete the configuration:

Preparing Each Node of the Cluster

For each node in the cluster, create the Instant Messaging runtime user and group under to run the components. The user ID (UID) and group ID (GID) numbers must be the same on all the nodes in the cluster.

• Runtime User ID: User name using which the Instant Messaging server runs. The default value is inetuser.
• Runtime Group ID: Group using which the Instant Messaging server runs. The default value is inetgroup.
  Although the configure utility creates the IDs, you can create the IDs before you invoke the configure utility as part of the preparation of each node. Create the runtime user and group ID on a node where you will not invoke the configure utility, which is usually secondary node.

Make sure that the username, group name and the corresponding user ID and group ID are same in the following files on all nodes:

• inetuser or the name that you select in the /etc/passwd directory on all the nodes in the cluster
• inetgroup or the name that you select in the /etc/group directory on all the nodes in the cluster

Refer to your operating system documentation for detailed information about users and groups.

Installing Instant Messaging

Selecting the Installation Directory IM_SVR_BASE

For Instant Messaging and Instant Messaging Sun Cluster agent IM_SCHA, the Communications Suite 6 installer uses the /opt/sun/comms directory on the Solaris operating system as the default installation directory. The value of the IM_SVR_BASE variable is /opt/sun/comms/im.

However, if you are using a shared disk for binaries, you must specify a cluster file system (CFS) or a failover file system (FFS) installation directory. For example, if /global/im/ is the installation directory, then the value of IM_SVR_BASE is /global/im/im.

If you are using a local disk, you should install the Instant Messaging in the same directory on each machine in the node.

Note Configuration files and runtime files reside on a CFS or on a highly-available FFS. Binaries are installed on local file systems on each node at the same location. Enables rolling upgrade of the Instant Messaging software. Binaries, configuration files and runtime files either reside on a CFS or on a highly-available FFS. The Instant Messaging installation is required only on one node as the binaries are shared across all the nodes. Instant Messaging upgrade needs a server down time.

Installing Instant Messaging Products and Packages

Install products and packages by using the Communications Suite 6 Update 1 installer program. For more information about the installer, refer to the Sun Java Communications Suite 6 Update 1 Installation Guide. The following table lists the products or packages required for a multiple node cluster configuration.

Instant Messaging HA Agent Installation

To install the Instant Messaging Sun Cluster HA agent, perform the following steps:

1. Type the Communications Suite installer command in the global zone.
   # commpkg install

   Note In case of Solaris 10 zones, run the above command from global and non-global zones.

2. Select the Instant Messaging Sun Cluster HA Agent software when prompted.
3. Type the Sun Cluster HA Agent preconfiguration command.
   # IM_SCHA_BASE/bin/init-config

   Note In case of Solaris 10 zones, run the above command only from the global zone.

Setting Up the Primary Node

Use the Sun Cluster command line interface to set up HA on the first node.

1. Register the Instant Messaging and HAStoragePlus resource.

   ./scrgadm -a -t SUNW.HAStoragePlus
   ./scrgadm -a -t SUNW.iim
   

2. Create a failover Instant Messaging resource group. For example, for a two node asymmetric cluster setup, the following command creates the Instant messaging resource group IM-RG with the primary node as NODE1 and the secondary, or failover, node as NODE2.
   ./scrgadm -a -g IM-RG -h IM_NODE1,IM_NODE2
3. Create a logical hostname resource in the Instant Messaging resource group and change the resource group state to online. For example, the following instructions create the logical hostname resource LOG_HOST_RS and bring the resource group IM-RG to online state.

   ./scrgadm -a -L -g IM-RG -l LOG_HOST_RS
   ./scrgadm -c -j LOG_HOST_RS -y    \
         R_description="LogicalHostname resource for LOG_HOST_RS"
   ./scswitch -Z -g IM-RG
   

4. Create and enable the HAStoragePlus resource. For example, the following commands create and enable the HAStoragePlus resource IM_HASP_RS.

   scrgadm -a -j IM_HASP_RS -g IM-RG -t
        SUNW.HAStoragePlus:4 -x FilesystemMountPoints=/IM_RUNTIME_DIR
   scrgadm -c -j IM_HASP_RS -y
        R_description="Failover data service resource for SUNW.HAStoragePlus:4"
   scswitch -e -j IM_HASP_RS
   

5. Create a symbolic link from the Instant Messaging /etc/opt/SUNWiim directory to the shared disk IM_RUNTIME_DIR directory on all the nodes of the cluster.

For example, type the following commands on all the nodes of the cluster:

# pwd
/etc/opt/

# ln -s /IM_RUNTIME_DIR SUNWiim

Invoking the configure Utility on the Primary Node

1. Invoke the configure utility. For example, from the /IM_SVR_BASE directory type the following command:

   # pwd
        /IM_SVR_BASE
   
   # ./configure
   

   For further information about the configure utility, see Configuring Instant Messaging After Installation.

2. When prompted for the Instant Messaging Server runtime files directory IM_RUNTIME_DIR, type either of the following commands:
   a. If you are using failover file system for the runtime files, type /local/im/.
   b. If you are using a cluster file system for the runtime files, type /global/im/.
3. If prompted for the Instant Messaging host name, type the logical host. Choose to accept the logical host even if the configure utility is unable to connect to the specified host. The logical host resource might be offline at the time when you invoke the configure utility.
4. Do not start Instant Messaging after configuration or on system startup.
5. Change the value of the iim_wd.period parameter to "60" and the iim_wd.maxRetries parameter to "2" in the {{ /IM_RUNTIME_CONFIG/iim.conf}} file.
6. Create and enable the Instant Messaging resource.
   In this example, the resource group name is IM_SVR_RS. Provide the logical host resource name and the HAStoragePlus resource name. For example,

   ./scrgadm -a -j IM_SVR_RS -g IM-RG
        -t SUNW.iim -x Server_root=/IM_SVR_BASE
        -x Confdir_list=/IM_RUNTIME_CONFIG 	(ex: /local/im/default/config )
        -y Resource_dependencies=IM_HASP_RS,LOG_HOST_RS
   
   ./scrgadm -e -j IM_SVR_RS
   

7. Test the successful creation of the Instant messaging resource group by performing a failover.
   ./ scswitch -z -g IM-RG -h IM_NODE2

   Note You do not need to configure the second node as the configuration is shared between all the nodes by soft links pointing to the shared location.

Installing and Configuring in a Symmetric HA Environment

This section contains instructions for configuring a symmetric high availability Instant Messaging system. To configure a symmetric high availability Instant Messaging system, perform the steps described in the following sections:

• Initial Tasks
• Installing and Configuring the First Instance of Instant Messaging
• Installing and Configuring the Second Instance of Instant Messaging

Initial Tasks
You must complete the following preparatory tasks before installing Instant Messaging on the nodes. The preparatory tasks are:
I. Creating File Systems
II. Installing the Instant Messaging HA Package
III. Preparing Each Node of the Cluster

I. Creating File Systems
Instant Messaging binaries, configuration files, and runtime files reside on the CFS or on the highly available FFS. For each Instant Messaging instance, installation is needed on only one node as the binaries are shared across all the nodes.

To create file systems, perform the following steps:

1. Create four file systems by using CFS or FFS.
   To create a system by using CFS, for example, the contents of the /etc/vfstab file should appear as follows.

   # Cluster File System/Global File System ##
   /dev/md/penguin/dsk/d500  /dev/md/penguin/rdsk/d500
       /INSTALL-ROOTIM1  ufs  2  yes  logging,global
   /dev/md/penguin/dsk/d400  /dev/md/penguin/rdsk/d400
       /share-disk-dirIM1  ufs  2  yes  logging,global
   /dev/md/polarbear/dsk/d200  /dev/md/polarbear/rdsk/d200
       /INSTALL-ROOTIM2  ufs  2  yes  logging,global
   /dev/md/polarbear/dsk/d300  /dev/md/polarbear/rdsk/d300
       /share-disk-dirIM2  ufs  2  yes logging,global
   

   Note The fields must be separated by tabs.

   To create a system by using FFS, for example, the contents of the /etc/vfstab file should appear as follows.

   # Failover File System/Local File System ##
   /dev/md/penguin/dsk/d500  /dev/md/penguin/rdsk/d500
       /INSTALL-ROOTIM1  ufs  2  yes  logging
   /dev/md/penguin/dsk/d400  /dev/md/penguin/rdsk/d400
       /share-disk-dirIM1  ufs  2  yes  logging
   /dev/md/polarbear/dsk/d200  /dev/md/polarbear/rdsk/d200
       /INSTALL-ROOTIM2  ufs  2  yes  logging
   /dev/md/polarbear/dsk/d300  /dev/md/polarbear/rdsk/d300
       /share-disk-dirIM2  ufs  2  yes logging
   

   Note The fields must be separated by tabs.

   
   

2. Create the following mandatory directories on all the nodes of the cluster.

   # mkdir -p /INSTALL-ROOTIM1 share-disk-dirIM1
        INSTALL-ROOTIM2 share-disk-dirIM2
   

II. Installing the Instant Messaging HA Package
Install the Instant Messaging Sun Cluster HA package in two nodes. You can use the Communication Suite 6 Update 1 installer to install the HA package.
To install the Instant Messaging Sun Cluster HA agent, perform the following steps:

1. 1. Run the Communications Suite 6 installation command.
      # commpkg install

      Note In case of Solaris 10 zone, run the above command from the global and non-global zones.

2. When prompted, select the Instant Messaging Sun Cluster HA Agent software.
3. Type the Sun Cluster HA Agent pre-configuration command.
   # <IM_SCHA_BASE>/bin/init-config

   Note In case of Solaris 10 zone, run the above command only from the global zone.

III. Preparing Each Node of the Cluster
For each node in the cluster, create the Instant Messaging runtime user and group under which the components will run. The user ID (UID) and group ID (GID) numbers must be the same on all nodes in the cluster.

• Runtime User ID: User name using which the Instant Messaging server runs. The default value is inetuser.
• Runtime Group ID: Group using which the Instant Messaging server runs. The default value is inetgroup.
  Although the configure utility creates these IDs, you can create the IDs before you invoke the configure utility as part of the preparation of each node. Create the runtime user and group ID on a node where you might not invoke the configure utility, which is usually secondary node.

Make sure that the username, group name and the corresponding user ID and group ID are same in the following files on all nodes:

• inetuser or the name that you select in the /etc/passwd directory on all the nodes in the cluster
• inetgroup or the name that you select in the /etc/group directory on all the nodes in the cluster

Refer to your operating system documentation for detailed information about users and groups.

Installing and Configuring the First Instance of Instant Messaging

To install the first instance of Instant Messaging, perform the following steps:

1. Verify whether the files are mounted.
   On the primary node Node1, type the following command:
   df -k
   The following message shows a sample output:

   /dev/md/penguin/dsk/d500     35020572
        34738 34635629   1%   /INSTALL-ROOTIM1
   /dev/md/penguin/dsk/d400     35020572
        34738 34635629   1%   /share-disk-dirIM1
   

2. Using the Communications Suite 6 installer, install Instant Messaging on the primary node.
   1. Type the Communications Suite installer command.
      # commpkg install

      Note In case of Solaris 10 zones, refer to the Sun Java Communications Suite 6 Installation Guide.

   2. At the Specify Installation Directories prompt, type the installation root INSTALL-ROOTIM1.
3. Create a symbolic link from the Instant Messaging the /etc/opt/SUNWiim directory to the shared disk IM_RUNTIME_DIR directory on all the nodes of the cluster. For example, type the following commands on a cluster node:

   # pwd
   /etc/opt/
   
   # ln -s /share-disk-dirIM1 SUNWiim
   

To configure Sun Cluster on the first node by using the Sun Cluster command-line interface, perform the following steps:

1. Register the following resource types.

   ./scrgadm -a -t SUNW.HAStoragePlus
   ./scrgadm -a -t SUNW.iim
   

2. Create a failover resource group.
   In the following example, the resource group is IM-RG1, IM_NODE1 is the primary node and IM_NODE2 is the failover node.
   ./scrgadm -a -g IM-RG1 -h IM_NODE1,IM_NODE2
3. Create a logical hostname resource for the node.
   Add the logical host name LOG_HOST_RS to the resource group. Instant Messaging listens on this hostname. The following example uses LOG-HOST-IM-RS1. Replace this value with the actual hostname.

   ./scrgadm -a -L -g IM-RG1 -l LOG-HOST-IM-RS1
   ./scrgadm -c -j LOG-HOST-IM-RS1 -y R_description=
        "LogicalHostname resource for LOG-HOST-IM-RS1"
   

4. Bring the resource group online.
   scswitch -Z -g IM-RG1
5. Create a HAStoragePlus resource and add it to the failover resource group.
   In this example, the resource is called IM_HASP_RS1. Replace the resource with your own resource name.

   Note The example is split for display purpose in this document.

   ./scrgadm -a -j IM-HASP-RS1 -g IM-RG1 -t
        SUNW.HAStoragePlus:4 -x FilesystemMountPoints=/INSTALL-ROOTIM1,
        /share-disk-dirIM1
   ./scrgadm -c -j IM-HASP-RS1 -y R_description="Failover data
        service resource for SUNW.HAStoragePlus:4"
   

6. Enable the HAStoragePlus resource.
   ./scswitch -e -j IM-HASP-RS1

To configure the first instance of Instant Messaging, perform the following steps:

1. Run the configure utility on the primary node.

   # cd /INSTALL-ROOTIM1/im
   # ./configure
   

   For more information about the configure utility, see configure Utility.

2. When prompted for the Instant Messaging Server Runtime Files Directory, type /share-disk-dirIM1 if you are using HAStoragePlus for the runtime files.
3. When prompted for the Instant Messaging host name, type the logical host.
   Choose to accept the logical host even if the configure utility cannot connect to the specified host. The logical host resource might be offline at the time when you invoke the configure utility.
4. Do not start Instant Messaging after configuration or on system startup.
5. Change the value of the iim_wd.period parameter to "60" and the iim_wd.maxRetries parameter to "2" in the {{ /IM_RUNTIME_CONFIG/iim.conf}} file.
6. Create and enable the Instant Messaging resource.
   In this example, the resource group name is IM_SVR_RS1.Provide the logical host resource name and the HAStoragePlus resource name.

   ./scrgadm -a -j IM_SVR_RS1 -g IM-RG1
        -t SUNW.iim -x Server_root=/INSTALL-ROOTIM1/im
        -x Confdir_list=/share-disk-dirIM1/default/config
        -y Resource_dependencies=IM-HASP-RS1,LOG-HOST-IM-RS1
   
   ./scrgadm -e -j IM_SVR_RS1
   

7. Test the successful creation of the Instant Messaging resource group by performing a failover.
   ./ scswitch -z -g IM-RG1 -h IM_NODE2

   Note You do not have to configure the second node as configuration is shared between all the nodes by soft links pointing to shared location.

   Installing and Configuring the Second Instance of Instant Messaging

To install the second instance of Instant Messaging, perform the following steps:

1. Verify whether the files are mounted. On the primary node IM_NODE2, type:
   df -k
   The following output is displayed:

   /dev/md/polarbear/dsk/d300   35020572
        34738 34635629   1%   /share-disk-dirIM2
   /dev/md/polarbear/dsk/d200   35020572
        34738 34635629   1%   /INSTALL-ROOTIM2
   

2. Using the Communications Suite 6 installer, install Instant Messaging on the primary node.
   1. Type the Communications Suite installation command.
      # commpkg install

      Note In case of Solaris 10 zones, refer to the Sun Java Communications Suite 6 Installation Guide.

   2. At the Specify Installation Directories prompt, specify the installation root INSTALL-ROOTIM2.
3. Create a symbolic link from the Instant Messaging /etc/opt/SUNWiim directory to the shared disk IM_RUNTIME_DIR directory on this cluster node.
   For example, type the following commands on all the nodes of the cluster:

   # pwd
   /etc/opt/
   
   # ln -s /share-disk-dirIM2 SUNWiim
   

Configuring Sun Cluster on the Second Node

To configure Sun Cluster on the second node by using the Sun Cluster command-line interface, perform the following steps:

1. Create a failover resource group.
   In the following example, the resource group is IM-RG2, IM_NODE2 is the primary node and IM_NODE1 is the failover node.
   ./scrgadm -a -g IM-RG2 -h IM_NODE2,IM_NODE1
2. Create a logical hostname resource for this node.
   Add the logical host name LOG_HOST_RS to the resource group. Instant Messaging will listen on this host name. The following example uses LOG-HOST-IM-RS2 in the place where you will substitute in the actual hostname.

   ./scrgadm -a -L -g IM-RG2 -l LOG-HOST-IM-RS2
   ./scrgadm -c -j LOG-HOST-IM-RS2 -y R_description=
        "LogicalHostname resource for LOG-HOST-IM-RS2"
   

3. Bring the resource group online.
   scswitch -Z -g IM-RG2
4. Create a HAStoragePlus resource and add it to the failover resource group.
   In this example, the resource is called IM-HASP-RS2. Replace it by your own resource name. Note that the lines are divided and show as two lines in the example for display purposes in this document.

   ./scrgadm -a -j IM-HASP-RS2 -g IM-RG2 -t
        SUNW.HAStoragePlus:4 -x FilesystemMountPoints=/INSTALL-ROOTIM2,
        /share-disk-dirIM2
   ./scrgadm -c -j IM-HASP-RS2 -y R_description="Failover data
        service resource for SUNW.HAStoragePlus:4"
   

5. Enable the HAStoragePlus resource.
   ./scswitch -e -j IM-HASP-RS2

To configure the second instance of Instant Messaging, perform the following steps:

1. Run the configure utility on the primary node.

   # cd /INSTALL-ROOTIM2/im
   
   # ./configure
   

   For more information about the configure utility, see configure Utility.

2. When prompted for the Instant Messaging Server Runtime Files Directory, type one of the following:
   If you are using an HAStoragePlus for the runtime files, type /share-disk-dirIM2
3. When prompted for the Instant Messaging host name, type the logical host.
   For example, accept the logical host even if the configure utility cannot connect to the specified host. The logical host resource might be offline when you invoke the configure utility.
4. Do not start Instant Messaging after configuration or on system startup.
   In an HA configuration, the Instant Messaging service requires the logical host to be online for Instant Messaging to work correctly.
5. Change the value of the iim_wd.period parameter to "60" and the iim_wd.maxRetries parameter to "2" in the {{ /IM_RUNTIME_CONFIG/iim.conf}} file.
6. Create the Instant Messaging resource and enable the resource.
   In this example, the resource group name is IM_SVR_RS2.Provide the logical host resource name, the HAStoragePlus resource name, and the port number. By default, Instant Messaging uses ports 5269,5222 and 45222. If the first instance uses these port numbers, use different port numbers for the second instance.

   ./scrgadm -a -j IM_SVR_RS2 -g IM-RG2
        -t SUNW.iim -x Server_root=/INSTALL-ROOTIM2/im
        -x Confdir_list=/share-disk-dirIM2/default/config
        -y Resource_dependencies=IM-HASP-RS2,LOG-HOST-IM-RS2
        -x port_list="5270/tcp","5223/tcp","45223/tcp"
   

7. Test the successful creation of the Instant messaging resource group by performing a failover.
   ./ scswitch -z -g IM-RG2 -h IM_NODE1

   Note You do not have to configure the second node as configuration is shared between all the nodes by soft links pointing to shared location.

Starting and Stopping the Instant Messaging HA Service

To start and stop the Instant Messaging HA service, use the Sun Cluster scswitch command.

Caution Do not use the imadmin start, imadmin stop, or imadmin refresh commands in a HA environment with Sun Cluster. Instead, use the Sun Cluster administrative utilities. For more information about the Sun Cluster scswitch command, refer to the Sun Cluster Reference Manual for Solaris OS.

To start the Instant Messaging HA service, type the following command:
# scswitch -e -j IM_SVR_RS

To stop the Instant Messaging HA service, type the following command:
# scswitch -n -j IM_SVR_RS

To restart the Instant Messaging HA Service, type the following command:
# scswitch -R -j IM_SVR_RS

Troubleshooting the Instant Messaging HA Configuration

To help troubleshooting error messages are stored in the error log. The logs are controlled by the syslog facility. For information about using the logging facility, see the HA Related Documentation and the syslog.conf man page.

Removing HA for Instant Messaging

To remove Instant Messaging from an HA environment, remove the Instant Messaging cluster agent SUNWiimsc.

When you remove the SUNWiimsc package as described in this procedure, any customization you made to the RTR file SUNW.iim is lost. If you want to restore them at a later time, you need to create a backup copy of SUNW.iim before removing SUNWiimsc.

To remove HA for Instant Messaging, perform the following steps:

1. Stop the Instant Messaging data service.
   scswitch -F -g IM_RG
2. Disable all resources in the Instant Messaging resource group IM_RG.

   # scswitch -n -j IM_SVR_RS
   # scswitch -n -j LOG_HOST_RS
   # scswitch -n -j IM-HASP-RS
   

3. Remove the resources from the Instant Messaging resource group.

   # scrgadm -r -j IM_SVR_RS
   # scrgadm -r -j LOG_HOST_RS
   # scrgadm -r -j IM-HASP-RS
   

4. Remove the Instant Messaging resource group.
   # scrgadm -r -g IM_RG
5. Remove the Instant Messaging resource type.
   # scrgadm -r -t SUNW.iim
6. Remove the SUNWiimsc package by using the Sun Java Enterprise System installer or type the pkgrm SUNWiimsc command.
   When you remove the package, any customization that you make to the RTR file is lost.
7. Remove any links that you have created during the HA configuration, if you are using a shared directory for configuration files and binaries.
   rm /etc/opt/SUNWiim

HA Related Documentation

A list of high availability documentation is as follows:

• Sun Java Enterprise System 5 Update 1 Technical Overview
• Sun Java Enterprise System 5 Update 1 Installation Guide for UNIX describes the Java Enterprise System installer, uninstaller, and the supported installation scenarios.
• Sun Java Enterprise System 5 Update 1 Release Notes provide current information about the Sun Java Enterprise System product.
• Sun Cluster Concepts Guide for Solaris OS provides a general background about the Sun Cluster software, data services, terminology resource types, resources, and resource groups.
• Sun Cluster Data Services Planning and Administration Guide for Solaris OS provides general information about planning and administration of data services.
• Sun Cluster System Administration Guide for Solaris OS provides software procedures for administering a Sun Cluster configuration.
• Sun Cluster Reference Manual for Solaris OS describes commands and utilities existing with the Sun Cluster software, including commands found only in the SUNWscman and SUNWccon packages.
• Sun Java System Communications Services 6 2005Q4 Deployment Planning Guide provides further information about how HA is implemented in Instant Messaging.