To Perform the Final Configuration Steps for the Second Instance

1. Using the Sun Cluster command-line interface, perform a fail over to the first node.

   For example:

   # /usr/cluster/bin/scswitch -z -g CAL-CS2-RG -h Node1

2. Edit the configuration file, ics.confby adding the parameters shown in the example that follows.

   ---

   Note –

   The values shown are examples only. You must substitute your own information for the values in the example.

   Back up the ics.conf file before starting this step.

   ---

   ! The following changes were made to configure Calendar Server
   ! Highly Available
   !
   local.server.ha.enabled="yes"
   local.server.ha.agent="SUNWscics"
   service.http.listenaddr="IPAddressCS2"
   local.hostname="LOG-HOST-CS2-RS"
   local.servername="LOG-HOST-CS2-RS"
   service.ens.host="LOG-HOST-CS2-RS"
   service.http.calendarhostname="LOG-HOST-CS2-RS-Domain.com"
   local.autorestart="yes"
   service.listenaddr = "IPAddressCS2"

   ---

   Note –

   The value for service.http.calendarhostname must be a fully qualified hostname.

   ---

3. Using the Sun Cluster command-line interface, create a Calendar Server resource group.

   Create a Calendar Server resource group and enable it.

   For example:

   ./scrgadm -a -j CAL-SVR-CS2-RS -g CAL-CS2-RG
         -t SUNW.scics -x ICS_serverroot=/cal-svr-baseCS2
         -y Resource_dependencies=CAL-HASP-CS2-RS,LOG-HOST-CS2-RS
   
   ./scrgadm -e -j CAL-SVR-CS2-RS

4. Using the Sun Cluster command-line interface to test the successful creation of the calendar resource group, perform a fail over to the second node, which is primary node for this Calendar Server instance.

   For example:

   ./scswitch -z -g CAL-CS2-RG -h Node2

   Your have now finished installing and configuring a symmetric HA Calendar Server.