HP Serviceguard Contributed Toolkit Suite version A.04.02.
© Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction...............................................................................................6 Storage considerations..............................................................................................................6 2 Apache Toolkit...........................................................................................7 Overview................................................................................................................................
Shared configuration..........................................................................................................30 Multiple PostgreSQL Instances Configuration..........................................................................30 Using PostgreSQL toolkit..........................................................................................................30 Configuring PostgreSQL toolkit packages...............................................................................
Prerequisites......................................................................................................................52 Installing and uninstalling Tomcat toolkit....................................................................................52 Files and directories created for Tomcat toolkit after installation................................................53 Setting up the Tomcat server in SG/LX environment.....................................................................
1 Introduction The HP Serviceguard Contributed Toolkit Suite is a collection of toolkits for popular applications to integrate them with the HP Serviceguard for Linux (SG/LX) environment. This toolkit suite is available as a tar file, which you must extract to get the RPM of each toolkit bundled with this suite.
2 Apache Toolkit Overview HP Serviceguard toolkit for Apache on Linux (Apache toolkit) enables you to integrate the Apache web server application with HP Serviceguard. Using Apache toolkit simplifies application integration, and eases deployment and maintenance of the application in a Serviceguard cluster environment. The Apache toolkit consists of a set of scripts that are used to start, stop, and monitor the Apache web server application. The toolkit simplifies the task of integrating Apache with SG/LX.
Installing and uninstalling the Apache toolkit The Apache toolkit is bundled within the SG/LX Contributed toolkit suite. The Apache toolkit must be installed on all the nodes of the cluster that are configured to run the Apache web server package. NOTE: Before installing this version of the toolkit, you must verify and remove any earlier version of this toolkit that might be installed on the system.
Table 2 Files for creating modular packages File name Description Available in directory apache.1 This is an attribute definition file, used Red Hat: ${SGCONF}/modules/ to generate a package ASCII template tkit/apache in modular style of packaging. tkit_module.sh This is the module script. This script is Red Hat: ${SGCONF}/scripts/ called by the master control script and tkit/apache acts as an interface between the tkit_module.sh master control script and the toolkit interface script (toolkit.sh).
DocumentRoot /shared/httpd/www-site2 For more information about configuring virtual hosts, see the Apache Web Server documentation. Supported configuration This section explains the following supported configurations for Apache toolkit packages: • Local configuration • Shared configuration • Multiple instance configuration Local configuration In a typical local configuration, files are not shared among the nodes.
Using SG Apache toolkit After installing the SG Apache toolkit, you can use the toolkit to: • Configure Apache toolkit packages in an SG/LX environment • Manage Apache toolkit packages Configuring Apache toolkit packages You can configure Apache toolkit packages using either legacy or modular style of packaging.
# cd ${SGCONF}/pkg/apache1 c. To create the package configuration file and the package control script, run the following commands: To create the package configuration file: # cmmakepkg -p pkg.conf To create the package control script: # cmmakepkg -s pkg.cntl 2. Edit the package configuration file. Enter the following command to open the package configuration file: # vi ${SGCONF}/pkg/apache1/pkg.conf You can edit the following variables in the package configuration file.
NOTE: HP recommends that you configure the server root directory and the document root directory on a shared storage. In the following example, the volume group /dev/vgtry1 is used as the server root directory and the document root directory. a. Mount the logical volume lvol on vgtry1 under the mount point /mnt/vgtry1/ apache. Use an IP address that is not used by any other application. Edit the following variables in the package control script.
NOTE: • To enable the AUTORUN parameter, run: # cmmodpkg –e APACHE1 • To enable package switching, run: # cmmodpkg –e -n node-1, -n node-2 ... -n node-n APACHE1 Once the package starts, it starts an Apache server instance comprising of the Apache daemon, httpd, which spawns a number of sub-processes to handle numerous http requests. It also launches the Apache monitor script.
Variable Example FS /mnt/vgtry2/apache IP aa.bb.ccc.d SUBNET xx.yy.zzz.a service_name apache2_service service_cmd ${SGCONF}/pkg/apache2/toolkit.sh monitor function customer_defined_run_cmds { ${SGCONF}/pkg/apache2/toolkit.sh start test_return 51 } function customer_defined_halt_cmds { ${SGCONF}/pkg/apache2/toolkit.sh stop test_return 52 } 5. To edit the Apache toolkit configuration file hahttp.conf, run: HTTPD_CONFIG_FILE="/mnt/vgtry2/apache/httpd.conf" 6.
3. Create the package configuration template using the cmmakepkg command: Configuration template: # cmmakepkg -m tkit/apache/apache pkg_apache.conf 4. Edit the following attributes of Apache toolkit parameters: Attribute Description TKIT_DIR This directory holds the toolkit configuration file. This parameter directs the cmapplyconf command to generate the hahttp.conf file under this directory. To put toolkit into maintenance mode, create apache.debug under this directory.
Attribute Description RETRY_TIMES The number of trials attempted by the toolkit script to check the Apache server daemon before giving up and exiting. The default value is 2. vg The volume group created for this package. fs_name This is the file system for the database. For example: /dev/vg01/lvol1 fs_directory This is the filesystem directory, which is Extended 2. For example: /shared/apache1 5. Validate the configuration using the cmcheckconf command: # cmcheckconf -P pkg_apache.conf 6.
3. Perform the maintenance actions. For example, you can change the configuration of the Apache instance or install an Apache patch. 4. To start monitoring application processes, run: # rm -f ${SGCONF}/pkg/apache1/apache.debug The following message is recorded in the Serviceguard package control script log: Starting Apache toolkit monitoring again after maintenance. NOTE: Ensure that the Apache server instance is up and running before removing the apache.debug file.
3 MySQL Toolkit Overview HP Serviceguard toolkit for MySQL on Linux (MySQL toolkit) enables you to configure MySQL database server application in an SG/LX cluster environment. The MySQL toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the MySQL database server. The toolkit simplifies the task of integrating MySQL with SG/LX.
Files and directories created for MySQL toolkit after installation The following table describes the scripts installed as part of the MySQL installation. Table 3 Files created after MySQL toolkit is installed File name Description Available in directory hamysql.conf This is the toolkit configuration file. It Red Hat: ${SGCONF}/mysqltoolkit contains a list of pre-defined variables that must be set for your unique environment. toolkit.
1. 2. 3. 4. Assuming that LVM is set up on the shared storage, create a filesystem (for example, /MySQL_1) on the LV and mount point (for example, /MySQL_1) on each of the nodes to mount the filesystem. Create the database on the lvol in /MySQL_1. Copy the configuration file /etc/my.cnf to /MySQL_1/my.cnf. Modify /MySQL_1/my.cnf to configure the DB for your unique environment.
Using MySQL toolkit After installing the MySQL toolkit, you can use this toolkit to: • Configure packages in an SG/LX environment • Manage packages Configuring MySQL toolkit packages You can configure MySQL toolkit packages using either legacy or modular style of packaging. Configuring legacy MySQL toolkit packages To configure legacy MySQL toolkit packages: 1. Create a directory for the package on all the cluster nodes using the following command: # mkdir ${SGCONF}/pkg/MySQL 2. 3. 4.
Attribute Description Example service_name The service name must be unique in mysql_monitor the cluster. service_cmd This is an interface to hamysql.sh. ${SGCONF}/pkg/MySQL/ toolkit.sh monitor function customer_defined_run_cmds { ${SGCONF}/pkg/MySQL/toolkit.sh start test_return 51 } function customer_defined_halt_cmds { ${SGCONF}/pkg/MySQL/toolkit.sh stop test_return 52 } 6. 7. Edit the MySQL toolkit configuration file hamysql.conf. Copy the package directory to the other nodes in the cluster.
Attribute Description file under this directory. This is synonymous with the package directory acronym. CONFIGURATION_FILE_PATH The file path of the configuration file for a MySQL server instance. For example: CONFIGURATION_FILE_PATH share/mysql/ my.cnf PID_FILE PID file of main MySQL process belongs to this package. This PID file, if present in the my.cnf, must correspond to the pid-file option on the configuration file. The PID file must be in the local hard disk.
6. Create the package using the cmapplyconf command, if the cmcheckconf command does not report any errors: # cmapplyconf -P pkg_MySQL.conf 7. Enable package switching for the MySQL toolkit package using: # cmmodpkg -e -n node1 -n node2 # cmmodpkg -e 8. Start the package using the cmrunpkg command. # cmrunpkg Managing packages You can manage packages by running, maintaining, halting, and deleting them.
NOTE: Ensure that the MySQL server instance is up and running before removing the mysql.debug file. Halting packages To halt a package: # cmhaltpkg Deleting packages To delete a package from the cluster: # cmdeleteconf -p This command prompts for a verification before deleting the files, unless you use the -f option.
4 PostgreSQL Toolkit Overview HP Serviceguard toolkit for PostgreSQL on Linux (PostgreSQL toolkit) enables you to integrate the PostgreSQL database server with HP Serviceguard. Using PostgreSQL toolkit simplifies application integration, and eases deployment and maintenance of applications in a cluster environment. The PostgreSQL toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the PostgreSQL database server.
# rpm –ivh serviceguard-postgresql-toolkit-.redhat.noarch.rpm The PostgreSQL toolkit directory is installed in the following directory: ${SGCONF}/postgresqltoolkit NOTE: To verify the PostgreSQL toolkit installation, you can run the # rpm –qa | grep postgresql-toolkit command, or you can verify whether all the toolkit scripts are present in the toolkit installation directory ${SGCONF}/postgresqltoolkit.
Setting up the PostgreSQL server in SG/LX environment Before configuring the Serviceguard package, you must complete the following configuration tasks for the application: 1. When the PostgreSQL database is installed, the default PostgreSQL server might be configured to start during system startup. If the server is already installed and configured, simply stop it with the following command. RedHat : "service postgresql stop" 2. Remove or move the following runlevel files.
NOTE: • Each node must have the same version of the PostgreSQL application. • Each node must have the same configuration directory where identical copies of the configuration files for each instance are placed in the local or shared hard disk. • Each node must have the same file system directories to access the same shared storage. Shared configuration In a shared configuration, the configuration and database files are placed all on the shared storage.
5. Edit the following attributes manually in the package configuration file: Attribute Description Example PACKAGE_NAME The package name must be unique in the cluster. pgsql_pkg NODE_NAME The name of the node that runs the package. node1 RUN_SCRIPT This is the script to start the service. ${SGCONF}/pkg/postgresql/ postgresql.cntl HALT_SCRIPT This is the script to halt the service. ${SGCONF}/pkg/postgresql/ postgresql.
For example: function customer_defined_halt_cmds { # Stop the PostgreSQL Database Server. ${SGCONF}/pkg/postgresql/toolkit.sh stop test_return 51 } 8. 9. Edit the PostgreSQL the toolkit configuration file hapgsql.conf. Copy the package directory to the other nodes in the cluster. For example, change to the parent directory of the package directory and enter the following command: # rcp -r –p ${SGCONF}/pkg/postgresql photon4:$PWD/ 10.
Attribute Description For Example: LOG_FILE /var/lib/pgsql/ pgsql1.log MAINTENANCE_FLAG This parameter is used to bring this toolkit into maintenance mode. If this parameter is set to yes, then it enables maintenance feature in the toolkit. PostgreSQL toolkit searches pgsql.debug file in the PostgreSQL toolkit package file directory where all the PostgreSQL toolkit files are located. If the file exists, monitoring is paused, and you can bring down PostgreSQL for maintenance.
1. Enable the maintenance for the package during package creation. To enable the maintenance mode, set the MAINTENANCE_FLAG to yes in the package configuration file or in the PostgreSQL toolkit configuration file, and then apply the configuration running the cmapplyconf command. 2. Create an empty file to pause PostgreSQL server processes monitoring. ${SGCONF}/pkgpg_pkg1/pgsql.debug as shown below: touch ${SGCONF}/pkgpg_pkg1/pgsql.
5 Samba Toolkit Overview HP Serviceguard toolkit for Samba on Linux (Samba toolkit) enables you to configure Samba in an SG/LX cluster environment. The Samba toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the Samba database server. The toolkit simplifies the task of integrating Samba with SG/LX. Advantages When Samba toolkit is deployed in an SG/LX environment, following are the advantages: • Provides monitoring for Samba daemons.
Table 7 Files created after Samba toolkit is installed File name Description Available in directory hasmb.conf This is the toolkit configuration file. It Red Hat: ${SGCONF}/sambatoolkit contains a list of pre-defined variables that needs to be set for your unique environment. hasmb.sh This is the toolkit main script that contains internal functions that start or stop an Samba instance. hasmb.
NOTE: If you plan only a single Samba instance running in a cluster, all default configuration of the standard Samba installation will be fitted into this single instance. You can choose to modify and use the default configuration file, /etc/samba/smb.conf. Alternatively, you can generate a new Samba configuration file for the Samba server.
NOTE: To use a shared file system, you must make all necessary preparations for the file system creation prior to creating the Samba toolkit package. For a local configuration, you must install and configure Samba in the same location on both the primary and all backup nodes and set up identical (or equivalent) configuration files in the same directory on all nodes. For a shared configuration, one or more shared file systems is used.
By bringing the Samba instances in service on one or more nodes, you can distribute the workload as desired. In addition, by adjusting the failover policy for each instances, the user can configure the Samba instance to fail over to a particular node, or to fail over to different nodes to distribute the workload when a failure occurs.
Attribute Description Example signal is sent to force the termination of the service. Control Script Parameters VG The VG created for this package. vg01 LV The logical volume created in VT. /dev/vg01/lvol1 FS This is the file system for DB. /shared/smb_1 FS_TYPE The FS type is Extended 2. ext2 FS_MOUNT_OPT Mount with read or write options. -o rw SUBNET This is the package subnet. ss.tt.uuu.v IP This is the relocatable IP address. aa.bb.ccc.
9. Create the package in the Serviceguard environment using cmapplyconf command, if the cmcheckconf command does not report any errors: # cmapplyconf -P smb_pkg.conf 10. Enable package switching for the Samba toolkit package using: # cmmodpkg -e -n node1 -n node2 smb_pkg # cmmodpkg -e smb_pkg 11. Start the package using the cmrunpkg command. # cmrunpkg smb_pkg Configuring Samba modular packages To configure modular Samba toolkit packages: 1.
Attribute Description If the file exists, monitoring is paused, and you can bring down Samba for maintenance. The package does not fail over to the adoptive node even though Samba instance is brought down for maintenance. After the maintenance work, ensure that Samba is brought up. You must delete the samba.debug file in the package directory. This enables the toolkit to continue monitoring Samba server application. NOTE: If the Maintenance flag is set to no, then this feature does not work. 5.
Samba toolkit pausing, monitoring, and entering maintenance mode. 3. Perform the maintenance actions. For example, you can change the configuration of the Samba instance, or install a Samba patch. 4. To start monitoring application processes, run: # rm -f ${SGCONF}/SMB_1/samba.debug The following message is recorded in the Serviceguard package control script log: Starting Samba toolkit monitoring again after maintenance.
6 Sendmail Toolkit Overview HP Serviceguard toolkit for Sendmail on Linux (Sendmail toolkit) enables you to configure Sendmail in an SG/LX cluster environment. The Sendmail toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the Sendmail server. The toolkit simplifies the task of integrating Sendmail with SG/LX. Sendmail application must be installed on all nodes that runs the Sendmail application in the SG/LX cluster.
NOTE: Before installing this version of the toolkit, you must verify and remove any earlier version of this toolkit that might be installed on the system. To check for a earlier version of Sendmail toolkit, run # rpm –qa | grep sendmail-toolkit.
Table 10 Files for creating modular packages File name Description Available in directory sendmail.1 This is an attribute definition file, used Red Hat: ${SGCONF}/modules/ to generate a package ASCII template tkit/sendmail in modular style of packaging. tkit_module.sh This is the module script. This script is Red Hat: ${SGCONF}/scripts/ called by the master control script and tkit/sendmail acts as an interface between the tkit_module.sh master control script and the toolkit interface script (toolkit.
/dev/sdb1; sdb1 is a shared disk Logical volume /dev/vgSM/lvolSM E.g. lvcreate -L M vgSM File system /pkgSM/sendmail E.g. mkfs /dev/vgSM/lvolSM, mount /dev/vgSM/lvolSM /pkgSM, then mkdir /pkgSM mkdir /pkgSM/sendmail mkdir /pkgSM/sendmail/mail mkdir /pkgSM/sendmail/mqueue mv /var/spool/mail /var/spool/mail.orig mv /var/spool/mqueue /var/spool/mqueue.orig ln -s /pkgSM/sendmail/mail /var/spool/mail ln -s /pkgSM/sendmail/mqueue /var/spool/mqueue 5.
1. Create a directory for the package on all the cluster nodes using the following command: # ${SGCONF}/pkg/Sendmail 2. 3. 4. Copy the toolkit files from ${SGCONF}/sendmailtoolkit to the package directory ${SGCONF}/pkg/Sendmail. cd to the package directory. Create the package configuration and control templates using the cmmakepkg command: Configuration template: # cmmakepkg -p pkgsm.conf Control template: # cmmakepkg -s pkgsm.cntl 5.
Attribute Description Example unlimited, the service is restarted for infinite number of times. If the value is none, the service is not restarted. If the value is a positive integer, the service is restarted for the specified number of times before failing. If service_restart is not specified, the default value is none. function customer_defined_run_cmds {${SGCONF}/pkg/Sendmail/toolkit.sh start test_return 51 } function customer_defined_halt_cmds { ${SGCONF}/pkg/Sendmail/toolkit.
Attribute Description maintenance mode, create sendmail.debug file under this directory. HA_SERVER_PID PID file that holds the process ID of the Sendmail server. This PID file must correspond to the sendmail PidFile directive in the sendmail.cf under /etc/ mail/directory For example: HA_SERVER_PID /var/run/sendmail.pid HA_SERVER_DB_FILES The db files in /etc/mail directory that is required to rebuild during the package start.
Running packages To start a package: # cmrunpkg Maintaining packages HP Serviceguard normally monitors critical processes, but there might be situations when a planned maintenance task (for example, changing the configuration) is required that affects those monitored processes. The maintenance flag can be used to signal to Serviceguard that it must not failover the instance to an adoptive node.
7 Tomcat Toolkit Overview HP Serviceguard toolkit for Tomcat on Linux (Tomcat toolkit) enables you to configure Tomcat server in an SG/LX cluster environment. The Tomcat toolkit consists of a set of shell scripts that are used by the package control script to start, stop, and monitor the Tomcat database server. The toolkit simplifies the task of integrating Tomcat with SG/LX.
Files and directories created for Tomcat toolkit after installation The following table describes the scripts installed and as part of the Tomcat installation. Table 11 Files created after Tomcat toolkit is installed File name Description Available in directory hatomcat.conf This is the toolkit configuration file. It Red Hat: ${SGCONF}/ contains a list of pre-defined variables tomcattoolkit that needs to be set to run the Tomcat toolkit package. hatomcat.
3. 4. Create a separate, distinct CATALINA_BASE directory for each Tomcat Serviceguard package. Configure all Tomcat instances to listen to package re-locatable IP addresses. For information on configuring virtual hosts, see Tomcat Server documentation. NOTE: For a local configuration, you must install and configure Tomcat in the same location on the primary and all backup nodes and set up the identical (or equivalent) configuration files in the same server root directory on all nodes.
Configuring Tomcat toolkit packages You can configure Tomcat toolkit packages using either legacy or modular style of packaging. Configuring legacy Tomcat toolkit packages To configure legacy Tomcat toolkit packages: 1. Create a directory for the package on all the cluster nodes using the following command: # mkdir ${SGCONF}/pkg/Tomcat 2. 3. 4. Copy the toolkit files from ${SGCONF}/tomcattoolkit to the package directory, ${SGCONF}/pkg/Tomcat. cd to the package directory.
Attribute Description Example service is restarted for the specified number of times before failing. If service_restart is not specified, the default value is none. function customer_defined_run_cmds { ${SGCONF}/pkg/Tomcat/toolkit.sh start test_return 51 } function customer_defined_halt_cmds { ${SGCONF}/pkg/Tomcat/toolkit.sh stop test_return 52 } 6. 7. Edit the tomcat the toolkit configuration file, hatomcat.conf. Copy the package directory to the other nodes in the cluster.
Attribute Description under this directory. To put the toolkit into maintenance mode, create tomcat.debug file under this directory. CATALINA_HOME Define the Catalina Home directory. This is the directory where Tomcat is installed. CATALINA_BASE Define the Catalina base directory. This is the base directory where Tomcat configuration files like server.xml reside. If this is not defined the toolkit uses CATALINA_HOME as the base directory.
Running packages To start a package: # cmrunpkg Maintaining packages HP Serviceguard normally monitors critical processes, but there might be situations when a planned maintenance task (for example, changing the configuration) is required that affects those monitored processes. The maintenance flag can be used to signal to Serviceguard that it should not failover the instance to an adoptive node.
8 Troubleshooting This section explains some of the problem scenarios that you might encounter while working with the Contrib toolkit in an SG/LX cluster. Problem scenario Possible cause cmcheckconf or cmapplyconf logs The TKIT_DIR specified in the the following message: WARNING! package configuration file is not Directory ${SGCONF}/ created. is not present. Package startup fails during cmrunpkg.
9 Support and other resources Information to collect before contacting HP Ensure that the following information is available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP HP provides the HP Serviceguard Contributed Toolkit Suite on Linux for free, so there is no support for it.
Term A term or phrase that is defined in the body text of the document, not in a glossary. User input Indicates commands and text that you type exactly as shown. Replaceable The name of a placeholder that you replace with an actual value. [] In command syntax statements, these characters enclose optional content. {} In command syntax statements, these characters enclose required content. | The character that separates items in a linear list of choices. ...
A Sample Apache toolkit package configuration file 62 package_name package_description package_type node_name script_log_file kit/apache/apache/TKIT_DIR tkit/apache/apache/HTTPD_CONFIG_FILE tkit/apache/apache/PID_FILE tkit/apache/apache/FAIL_CRITERIA tkit/apache/apache/MAINTENANCE_FLAG tkit/apache/apache/MONITOR_INTERVAL apache_pkg "Serviceguard Package" failover * ${SGCONF}/apache_pkg/$SG_PACKAGE.log ${SGCONF}/apache_pkg /etc/httpd/conf/httpd.conf_1 /var/run/httpd.
B Sample MySQL toolkit package configuration file package_name package_description package_type node_name script_log_file tkit/mysql/mysql/TKIT_DIR tkit/mysql/mysql/CONFIGURATION_FILE_PATH tkit/mysql/mysql/PID_FILE tkit/mysql/mysql/MAINTENANCE_FLAG tkit/mysql/mysql/RETRY_TIMES tkit/mysql/mysql/MONITOR_INTERVAL tkit/mysql/mysql/TIME_OUT service_name service_cmd service_restart service_fail_fast_enabled service_halt_timeout priority vgchange_cmd vg fs_name fs_server fs_directory fs_type fs_mount_opt mysql_pk
C Sample PostgreSQL toolkit package configuration file package_name package_description package_type node_name script_log_file tkit/pgsql/pgsql/TKIT_DIR tkit/pgsql/pgsql/DATA_DIRECTORY tkit/pgsql/pgsql/LOG_FILE tkit/pgsql/pgsql/MAINTENANCE_FLAG tkit/pgsql/pgsql/MONITOR_INTERVAL service_name service_cmd service_restart service_fail_fast_enabled service_halt_timeout vg fs_name fs_server fs_directory fs_type fs_mount_opt 64 Sample PostgreSQL toolkit package configuration file pg_pkg "Serviceguard PostgreSQ
D Sample Samba toolkit package configuration file package_name package_description package_type node_name script_log_file smb_pkg "Serviceguard samba toolkit Package" failover * ${SGCONF}/smb_pkg/$SG_PACKAGE.log tkit/samba/samba/TKIT_DIR tkit/samba/samba/BASE_CONF_FILE tkit/samba/samba/MAINTENANCE_FLAG tkit/samba/samba/MONITOR_INTERVAL ${SGCONF}/smb_pkg /etc/samba/smb.conf yes 30 service_name service_cmd samba.monitor "${SGCONF}/scripts/tkit/samba/tkit_module.
E Sample Sendmail toolkit package configuration file package_name package_description package_type node_name script_log_file sendmail_pkg "Serviceguard sendmail toolkit Package" failover * ${SGCONF}/sendmail_pkg/$SG_PAC KAGE.
F Sample Tomcat toolkit package configuration file package_name package_description package_type node_name script_log_file tom_pkg "Serviceguard tomcat toolkit Package" failover * ${SGCONF}/$SG_PACKAGE.
Glossary ${SGCONF} /usr/local/cmcluster/conf for RHEL ADF Attribute definition file CIFS Common Internet File System Package A grouping of application services (individual Linux Processes) under Serviceguard SMB Server Message Block VG Volume Group 68 Glossary
Index A Apache Toolkit Advantages, 7 Overview, 7 Prerequisites, 7 Apache toolkit after Installation files and directories, 8 H HP Serviceguard Contributed Toolkit Suite Introduction, 6 troubleshooting, 59 I Installation uninstallation, 8, 19, 27, 35, 44, 52 M Managing packages halting packages, 18, 26, 34, 43, 51, 58 maintaining packages, 58 running packages, 17, 25, 33, 42, 51, 58 S Storage considerations, 6 Supported configuration, 10 T Tomcat Toolkit Managing packages, 57 typographic conventions, 60
