HP Serviceguard Contributed Toolkit Suite Version A.04.02.02 on Linux User Guide (December, 2012)

Table 25 List of attributes that you can edit
ExampleDescriptionAttribute
Configuration file parameters
tomcat_pkg1The package name must be unique
in the cluster.
PACKAGE_NAME
node1The name of the node that runs the
package.
NODE_NAME
$SGCONF/pkg/Tomcat/
tomcat_pkg.cntl
This is the script to start the service.RUN_SCRIPT
$SGCONF/pkg/Tomcat/
tomcat_pkg.cntl
This is the script to halt the service.HALT_SCRIPT
tomcat1_monitorThe service name must be unique in
the cluster.
service_name
Control Script Parameters
vg01The VG created for this package.VG[0]
/shared/tomcat_1This is the file system for DB.FS[0]
/dev/vg01/lvol1The logical volume created in VT.LV[0]
ext2The FS type is Extended 2.FS_TYPE[0]
-o rwMount with read or write options.FS_MOUNT_OPT[0]
192.168.0.0This is the monitored subnet.SUBNET
192.168.0.01This is the floating IP address.IP
tomcat1_monitorThe service name must be unique in
the cluster.
service_name
$SGCONF/pkg/Tomcat/
toolkit.sh monitor
This is an interface to
hatomcat.sh.
service_cmd
-r 0The value for service_restart
can be unlimited, none or any
service_restart
positive integer value. If the value is
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.
To run the toolkit.sh script with the start option, edit the customer_defined_run_cmds
function in the package control script as follows:
function customer_defined_run_cmds
{
$SGCONF/pkg/Tomcat/toolkit.sh start
test_return 51
}
To run the toolkit.sh script with the start option, edit the customer_defined_run_cmds
function in the package control script as follows:
function customer_defined_halt_cmds
{
$SGCONF/pkg/Tomcat/toolkit.sh stop
56 Tomcat Toolkit