test

Sun Java System Calendar Server 6 2005Q4 Administration Guide

Installation and Configuration

The Calendar Server HA configuration examples in this section use the following names:

Name in Example  

Description  

/global/cal/

Global file system mount point 

cal-logical-host

Logical host name 

cal-logical-host-ip

Logical host IP numeric address 

cs-admin@cal-logical-host

Email address for the Calendar Server administrator 

cal-node-1

Node 1 

cal-node-2

Node 2 

cal-resource-group

Calendar resource group 

cal-resource-group-store

Calendar Server storage resource 

cal-resource

Calendar Server resource 

ProcedureTo Install and Configure a Calendar Server HA Configuration

This is a high level list of the steps necessary to install and configure a Calendar Server HA configuration.

  1. Log in as Superuser

  2. Prepare Each Node in the Cluster

  3. Install Sun Java Enterprise System Products and Packages

  4. Configure the Logical Host

  5. Activate the Storage Resource

  6. Run Postinstallation Configuration Programs

  7. Locate Automatic Backup Directories on Shared Storage

  8. Relocate the Calendar Server config Directory

  9. Edit the Calendar Server ics.conf File

  10. Start the HA Calendar Server

  11. Verify the HA Configuration

Log in as Superuser

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

Prepare Each Node in the Cluster

On each node in the cluster, perform these steps:

  1. Create the Calendar Server runtime user and group under which Calendar Server will run as follows:

    1. Add icsgroup (or the value you selected) to the /etc/group file.

    2. Add icsuser (or the value you selected) to the /etc/passwd file.

    Tip –

    The default names are icsuser and icsgroup. You can use other names if you prefer, but the uid and gid numbers must be the same on all nodes in the cluster. The user name should not be root.

    You must provide the user and group names when you Run Postinstallation Configuration Programs.

  2. Add or set the following fields in the /etc/vfstab file:

Install Sun Java Enterprise System Products and Packages

The installation of Sun Java Enterprise System products, including Calendar Server, has significantly changed from earlier Sun branded products (for example, Sun ONE, and iPlanet). To install Sun Java Enterprise System products, you must use the Sun Java Enterprise System installer.

For information about the installer, refer to the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.

The following table describes the Sun products and packages required for a Calendar Server HA configuration.

Product or Package 

Node 1 

Node 2 

Sun Cluster Software 

yes 

yes 

Calendar Server (6.0 and later) 

yes 

no 

Sun Cluster Agent for Calendar Server (SUNWscics package)

yes 

yes 

Shared components (SUNWicu, SUNWldk, SUNWpr, SUNWsasl, and SUNWtls packages)

yes 

yes 

Node 1

On node 1, install all selected products and packages using the Java Enterprise System installer. When you install Calendar Server, you must specify a directory other the default directory. See Selecting the Calendar Server Installation Directory.

Node 2

On node 2, follow these steps:

  1. Install Sun Cluster and the Sun Cluster Agent for Calendar Server (SUNWscics package) using the Java Enterprise System installer.

  2. Note You cannot install only the Sun Cluster Agent for Calendar Server. When you chose the Sun Java System Agents for Sun Cluster, the Java Enterprise System installer installs all agents.

  3. Install shared components (SUNWicu, SUNWldk, SUNWpr, SUNWsasl, and SUNWtls packages) using the pkgadd command. See Installing Shared Components.

Selecting the Calendar Server Installation Directory

For Calendar Server, the Java Enterprise System installer uses the following default installation directory: /opt

However, for an HA configuration, you must specify a global installation directory. For example: /global/cal/opt/

Installing Shared Components

To make the required shared components available on node 2, you must install the following packages:

These packages are available in the following directories:

.../Solaris_sparc/Product/shared_components/Packages/SUNWldk
 .../Solaris_sparc/Product/shared_components/Solaris_8/Packages
 .../Solaris_sparc/Product/shared_components/Solaris_9/Packages

To install these packages, change to one of the directories shown above and use the pkgadd command. For example:

# pkgadd -d . SUNWicu SUNWpr SUNWsasl SUNWtls

Configure the Logical Host

To configure the logical host:

  1. Create a Calendar Server failover resource group named cal-resource-group:


    # scrgadm -a -g cal-resource-group -h cal-node-2,cal-node-1

  2. Add the logical host name named cal-logical-host to the resource group. Calendar Server will listen on this host name.


    # scrgadm -a -L -g cal-resource-group -l cal-logical-host

  3. Bring the resource group online:


    # scswitch -Z -g cal-resource-group

Activate the Storage Resource

To activate the storage resource:

  1. Register the storage resource specifying the mount point as the ServicePaths property:


    # scrgadm -a 
    -j cal-resource-group-store
    -g cal-resource-group
    -t SUNW.HAStorage
    -x ServicePaths=/global/cal
    -x AffinityOn=True

  2. Enable the storage resource:


    # scswitch -e -j cal-resource-group-store

    If SUNW.HAStoragePlus has also chosen to setup a global file system (GFS), the FileSystemMountPoints property must be set instead of ServicePaths.

Run Postinstallation Configuration Programs

After you install Calendar Server, run the Directory Server Setup script (comm_dssetup.pl) and the Calendar Server configuration program (csconfigurator.sh) as described in Chapter 2, Directory Preparation Script (comm_dssetup.pl).

The following table describes the specific configuration information that you must provide for an HA configuration.

Table 7–1 Calendar Server Configuration Options for an HA Configuration

Configuration Panel 

Description  

Runtime Configuration 

Runtime User ID and Group ID

  • Runtime user ID is the user name under which Calendar Server will run. This name should not be root. The default is icsuser.

  • Runtime Group ID is the group under which Calendar Server will run. The default is icsgroup.

    Although the configuration program can create these names for you, you should create them before you run the configuration program, as part of the preparation of each node as described earlier in this chapter.

    These names must be in the following files:

  • icsuser (or the name you select) in /etc/passwd on all nodes in the cluster

  • icsgroup (or the name you select) in /etc/group on all nodes in the cluster

    Calendar Server Startup

    Do not check either of these options.

  • Start after successful installation

  • Start on system startup

Select Directories 

For the location of the database, temporary, and log files, select global partitions. For example: 

  • Database:/global/cal/var/csdb

  • Temporary Files: /global/cal/var/tmp

  • Logs: /global/cal/var/logs

  • Backups:/global/cal/var/hotbackupdb, and /global/cal/var/archivedb

Locate Automatic Backup Directories on Shared Storage

When configuring automatic backups for HA, backup directories must reside on shared storage partitions to prevent incomplete copies on individual nodes of the cluster. Pay particular attention to the size of the partition, since backup directories are large.

Disk space calculations fail for symbolic links. Therefore, do not use symbolic links for automatic backup directories.

Relocate the Calendar Server config Directory

The Calendar Server stores configuration files in the config directory. In an earlier release, the config directory was relocated. Its location is:

/etc/opt/SUNWics5/config/

Symbolic links to the old config directory are kept in the following directories:

After running the Calendar Server configuration program, csconfigurator.sh, remove the symbolic link in each of the old directories and replace it with a link to the new directory as described in the procedures that follows. Note that these procedures preserve the settings from the original configuration files found in /etc/opt/SUNWics5/config.

Before you start, make sure the contents of the config directory are owned by icsuser and icsgroup (or your choices you specified for the runtime User ID and Group ID):

# ls -ld config
 ... icsuser icsgroup ... config/

To Change the Symbolic Link Found in /opt/SUNWics5/cal:

  1. Change to the /global/cal/opt/SUNWics5/cal directory, For example:


    # cd /global/cal/opt/SUNWics5/cal/

    where /global/cal/ is the file system mount point.

  2. Check that config is a symbolic link to the new config directory. For example:


    # ls -l config
 ... config -\> /etc/opt/SUNWics5/config/

  3. In the /opt/SUNWics5/cal/ directory, remove the config symbolic link:


    # cd /opt/SUNWics5/cal
# rm config

  4. Copy the contents of the /etc/opt/SUNWics5/config directory into the new HA directory, preserving the ownership and permissions:


    # cd /global/cal/opt/SUNWics5/cal
# cp -pr /etc/opt/SUNWics5/config .

To Change the Symbolic Link Found in /opt/SUNWics5/lib:

  1. In the /global/cal/opt/SUNWics5/cal/lib directory, check that config is a symbolic link to /etc/opt/SUNWics5/config.


    # cd /global/cal/opt/SUNWics5/cal/lib
 # ls -l config
 ... config -\> /etc/opt/SUNWics5/config/

  2. Remove the config symbolic link:


    # rm config

  3. Create a new symbolic link to the new config location:


    # ln -s ../config config

  4. Verify the new link:


    # ls -l config
 ... config -\> ../config/

To Change the Symbolic Link Found in /opt/SUNWics5/sbin:

  1. In the /global/cal/opt/SUNWics5/cal/sbin directory, check that config is a symbolic link to /etc/opt/SUNWics5/config.


    # cd /global/cal/opt/SUNWics5/cal/sbin
 # ls -l config
 ... config -\> /etc/opt/SUNWics5/config/

  2. Remove the config symbolic link:


    # rm config

  3. Create a new symbolic link to the new config location:


    # ln -s ../config config

  4. Verify the new link:


    # ls -l config
 ... config -\> ../config/
    Note –

    If you need to uninstall Calendar Server, use the Java Enterprise System uninstaller, which removes the SUNWics5 and SUNWica5 packages.

    For a Calendar Server HA configuration, however, you must first remove the relocated config directory and all of its contents before you run the uninstaller. For example:


    # cd /global/cal/opt/SUNWics5/cal/
 # rm -rf config

    If you do not remove the config directory, the uninstall operation fails for the SUNWics5 package.

Edit the Calendar Server ics.conf File

In the /opt/SUNWics5/cal/config directory, edit the ics.conf configuration file as follows:

  1. Add the following parameters:


    local.server.ha.enabled="yes"
 local.server.ha.agent="SUNWscics"

  2. Rename the service.listenaddr parameter to service.http.listenaddr and then set the parameter to the IP address of the logical host. For example:


    service.http.listenaddr = "cal-logical-host-ip"

    where “cal-logical-host-ip” is the numeric IP address of the logical host. For example: 123.321.12.2.

  3. Change all parameters that refer to a local host name to the logical host name. For example:


    local.hostname="cal-logical-host"
 local.servername="cal-logical-host"
 service.ens.host="cal-logical-host"
 service.http.calendarhostname="cal-logical-host.sesta.com"

Start the HA Calendar Server

Before you start the HA Calendar Server, register the calendar resource type SUNWscics and create a calendar resource as follows:

  1. Register the calendar resource type:


    # scrgadm -a -t SUNW.scics

  2. Create the calendar resource:


    # scrgadm -a 
        -j cal-resource 
        -g cal-resource-group
        -t SUNW.scics 
        -x Confdir_list=/global/cal/cal-resource-group 
        -y Resource_dependencies=cal-resource-group-store 
        -y Port_list=80/tcp

  3. Enable the resource and start Calendar Server:


    # scswitch -e -j cal-resource

Verify the HA Configuration

After you start Calendar Server check that all required processes or daemons (csadmind, enpd, csnotifyd, and cshttpd) are running.

Additionally, conduct a switchover of the service to the backup node to ensure the high availability. For example, if the service is running on cal-node-1, issue the following command to switch the service to cal-node-2.

# scswitch -z -g cal-resource-group
                            -h cal-node-2

Then check that all processes are started on cal-node-2.

For troubleshooting, error messages are written to the console and /var/adm/messages.

The /var/cluster/rgm/rt/SUNW.scics/loglevel file contains the logging level. Use “9” for maximum verbosity.

For information about using the logging facility, refer to the Related Documentation.