/etc/cmcluster/pkg/http_pkg1/toolkit.sh start

test_return 51

}

For example:

function customer_defined_halt_cmds

{

#Stop the Apache Web Server. /etc/cmcluster/pkg/http_pkg1/toolkit.sh stop test_return 51

}

NOTE: If CFS mounted file systems are used then volume groups, logical volumes and file systems must not be configured in the package control script but dependency on SG CFS packages must be configured.

3.Configure the Apache user configuration file hahttp.conf as explained in the next section.

4.Copy this package configuration directory to all other package nodes.

Use the same procedure to create multiple Apache packages (multiple Apache instances) that will be running on the cluster.

Setting up The Toolkit

Toolkit Overview

After installing the toolkit, four scripts and one README file will be installed in the location /opt/ cmcluster/toolkit/apache. Two more scripts and one file will be installed which will be used only for modular packages. The two scripts will be in the /etc/cmcluster/scripts/ ecmt/apache directory. The third file will be in the /etc/cmcluster/modules/ecmt/apache directory.

For legacy packages, one user configuration script (hahttp.conf) and three functional scripts (toolkit.sh, hahttp.sh and hahttp.mon) will work together to integrate Apache web server with the Serviceguard package control script.

Table 25 (page 105) lists the scripts used in legacy packages are:

Table 25 Scripts in Legacy Packages

Script Name

Description

User Configuration file (hahttp.conf)

This script contains a list of pre-defined variables that may be customized

 

for the user's environment. This script provides the user a simple format of

 

the user configuration data. This file will be included (that is, sourced) by

 

the toolkit main script hahttp.sh.

Main Script (hahttp.sh)

This script contains a list of internal-use variables and functions that support

 

the start and stop of an Apache instance. This script will be called by the

 

Toolkit Interface Script to do the following:

 

On package start, it starts the Apache server instance.

 

On package stop, it stops the Apache server instance.

Monitor Script (hahttp.mon)

Monitoring functionality will be initiated by calling the toolkit with the

 

"monitor" parameter as "toolkit.sh monitor".

Interface Script (toolkit.sh)

This script is an interface between the Serviceguard package control script

 

and the toolkit main script (hahttp.sh).

Setting up The Toolkit 105

Page 105
Image 105
HP Serviceguard Toolkit for Oracle Data Guard manual Scripts in Legacy Packages