Serviceguard Toolkits for Contrib User Guide Version A.12.00.00

ManualsBrandsHP ManualsSoftwareHP SAP Linux Serviceguard Cluster Extension

Files and directories created for Apache toolkit after installation

The following table describes the scripts installed as part of the Apache toolkit installation.

Table 1 Apache toolkit files

Available in directoryDescriptionFile name

$SGROOT/apachetoolkitThis is the toolkit main script that

contains internal functions that start or

stop an Apache instance.

hahttp.sh

This is the toolkit monitor script that

contains internal functions for

monitoring an Apache server instance.

hahttp.mon

This is the toolkit interface script that

acts as an interface between the

toolkit.sh

package tkit_module.sh control

script and the toolkit main script,

hahttp.sh.

$SGCONF/modules/tkit/apacheThese are attribute definition files,

used to generate package ASCII

apache.1

apache.2

templates in modular style of

packaging.

$SGCONF/scripts/tkit/apacheThis is the module script. This script is

called by the master control script and

tkit_module.sh

acts as an interface between the

master control script and the toolkit

interface script (toolkit.sh).

Setting up the Apache server in SG/LX environment

Before creating and configuring Serviceguard packages, you must complete the following

configurations for the Apache web server application on all package nodes:

1. When the Apache server is installed, the default Apache instance might be configured to

automatically startup during system startup via the runlevel (rc) scripts in the /etc/rc.d

directory. In such a case, disable the automatic startup of Apache.

2. Configure the Apache server.

For more information about configuring the Apache server, see Apache Web Server

documentation.

3. Create a separate, distinct server root directory and server configuration file for each Apache

SG/LX package.

This server root directory corresponds to the Apache ServerRoot directive specified in the

configuration file. Each package corresponds to a unique Apache instance with its associated

configuration and server root directory.

4. Configure all Apache instances to listen to package re-locatable IP addresses using Listen

directives.

For example, the configuration file for an Apache instance that combines IP-based and

name-based virtual hosts would include the following directive:

Listen aaa.bbb.c.d:ee

NameVirtualHost aaa.bbb.c.d:ee

ServerName web.site1.url

DocumentRoot /shared/httpd/www-site1

</VirtualHost>

Files and directories created for Apache toolkit after installation 9