Modular Package Support in Serviceguard for Linux and ECM Toolkit

Note:

In the case of NFS

lock_migration.sh External Script for Lock Migration

These files are installed in the locations below:

On HP-UX:

$SGCONF/modules/ecmt/<app>/<app>

$SGCONF/modules/ecmt/<app>/<app>.1

$SGCONF/scripts/ecmt/<app>/tkit_module.sh

$SGCONF/scripts/ecmt/<app>/tkit_gen.sh

where $SGCONF is /etc/cmcluster

On Linux:

$SGCONF/modules/tkit/<app>/<app>

$SGCONF/modules/tkit/<app>/<app>.1

$SGCONF/scripts/tkit/<app>/tkit_module.sh

$SGCONF/scripts/tkit/<app>/tkit_gen.sh

$SGCONF/scripts/tkit/nfs/lock_migration.sh

where $SGCONF value for various Linux distributions are as given below:

Red Hat : /usr/local/cmcluster/conf

SLES : /opt/cmcluster/conf

Install and Configuration directory operations

By default, the toolkit scripts that were previously used in legacy packages will be installed in the

following directories.

HP-UX : /opt/cmcluster/toolkit/<app>

Red Hat : /usr/local/cmcluster/<app>toolkit

SLES : /opt/cmcluster/<app>toolkit

This directory is called the Installation directory. The user can copy these scripts to a configuration

directory and define this location in the parameter ‘TKIT_DIR’ in the modular package configuration

file. Serviceguard uses the toolkit scripts in the configuration directory by default. If the scripts are

not found in the configuration directory, Serviceguard takes them from the installation directory.

This feature is useful for customers wanting to use modified versions of the toolkit(s).

Setting up a modular package

With the legacy method of packaging, the user had to configure three scripts: the package

configuration script, the package control script and the toolkit configuration file. With the

introduction of the modular method of packaging, the user has to modify only one file – the

package configuration file.

The package configuration file contains Serviceguard specific parameters that need to be

configured appropriately by the user. The package configuration file also has service parameters

and some toolkit specific pre-configured default parameters. This simplifies configuration of a

package for the user.