6.7.3 Installing and Configuring the Second Instance of Calendar Server (Sun Java System Calendar Server 6.3 Administration Guide)

Sun Java System Calendar Server 6.3 Administration Guide

6.7.3 Installing and Configuring the Second Instance of Calendar Server

The primary node for the second Calendar Server instance is the second node (Node2).

To Install Calendar Server on the Second Node

Verify the files are mounted.

On the primary node (Node2), enter the following command:

df -k

The following is an example of the output you should see:

/dev/md/penguin/dsk/d500     35020572   
     34738 34635629   1%   /install-rootCS1
/dev/md/penguin/dsk/d400     35020572   
     34738 34635629   1%   /share-disk-dirCS1
/dev/md/polarbear/dsk/d300   35020572   
     34738 34635629   1%   /share-disk-dirCS2
/dev/md/polarbear/dsk/d200   35020572   
     34738 34635629   1%   /install-rootCS2
/dev/md/polarbear/dsk/d600   35020572   
     34738 34635629   1%   /var-cal-dirCS1
/dev/md/polarbear/dsk/d700   35020572   
     34738 34635629   1%   /var-cal-dirCS2

Using the Sun Java Systems Communications Suite installer, install Calendar Server on the new Primary Node (second node).
1. At the Specify Installation Directories panel, specify the installation root for the second node (/install-rootNode2):
  
  For example, if your Node 2 machine is named blue and your root directory is ocean, your installation directory would be /ocean/blue.
2. Select the Configure Later option.

To Configure Sun Cluster for the Second Instance

Using the Sun Cluster command-line interface, configure the second instance of Calendar Server as described in the following steps:

Create a fail over resource group.

In the following example, the resource group is CAL-CS2-RG, and the two nodes are named Node2 as the primary node and Node1 as the fail over node.
```
./scrgadm -a -g CAL-CS2-RG -h Node2,Node1
```

Create a logical hostname resource.

The calendar client listens on this logical hostname. The example that follows uses LOG-HOST-CS2-RS in the place where you will substitute in the actual hostname.
```
./scrgadm -a -L -g CAL-CS2-RG -l LOG-HOST-CS2-RS
./scrgadm -c -j LOG-HOST-CS2-RS -y R_description="LogicalHostname 
     resource for LOG-HOST-CS2-RS"
```

Bring the resource group online.
```
scswitch -Z -g CAL-CS2-RG
```

Create an HAStoragePlus resource and add it to the fail over resource group.

In this example, the resource is called CAL-SVR-CS2-RS. You will substitute you own resource name.

./scrgadm -a -j CAL-SVR-CS2-RS -g CAL-CS2-RG -t 
     SUNW.HAStoragePlus:4 -x FilesystemMountPoints=/install-rootCS2,
     /share-disk-dirCS2,/var-cal-dirCS2
./scrgadm -c -j CAL-HASP-CS2-RS -y R_description="Failover data 
     service resource for SUNW.HAStoragePlus:4"

Enable the HAStoragePlus resource.
```
./scswitch -e -j CAL-HASP-CS2-RS
```

To Configure the Second Instance of Calendar Server

Run the configuration program again on the secondary node.
```
# cd /cal-svr-baseCS2/sbin/

# ./csconfigurator.sh
```
For further information about running the configuration script, see the Sun Java System Calendar Server 6.3 Administration Guide.

On the Runtime Configuration panel, deselect both of the Calendar Server start up options.

On the Directories to Store Configuration and Data Files panel, provide the proper directories as shown in the following list:

Config Directory

share-disk-dirCS2/config

Database Directory

/share-disk-dirCS2/csdb

Attachment Store Directory

/share-disk-dirCS2/store

Logs Directory

/share-disk-dirCS2/logs

Temporary Files Directory

/share-disk-dirCS2/tmp

When you have finished specifying the directories, choose Create Directory.

On the Archive and Hot Backup panel, provide the appropriate directory names as shown in the following list:

Archive Directory

/share-disk-dirCS2/csdb/archive

Hot Backup Directory

/share-disk-dirCS2/csdb/hotbackup

After specifying these directories, choose Create Directory.

Verify that the configuration was successful.

The configuration program will display a series of messages. If they all start with PASSED, which means it was successful. For an example of the output you might see, check the example at: 6.11 Example Output from the Calendar Configuration Program (Condensed).

To Perform the Final Configuration Steps for the Second Instance

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
```

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.

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

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.