HP Serviceguard Developer's Toolbox Version B.12.00.00 For HP-UX and Linux

package, so that package resources (including volume groups, relocatable IPs, and so on.)
are intact and available.
To continue monitoring by exiting the maintenance mode, remove the toolbox.debug file.
Ensure that the application instance is running properly before exiting the maintenance mode,
because the monitoring of the instance resumes after the package exits the maintenance mode.
The default setting for this variable in the Toolkit template is yes. When the package is running,
you can initiate the maintenance mode by starting the file toolbox.debug in the Toolkit
configuration directory.
To resume application monitoring after maintenance, manually remove the file toolbox.debug
from the Toolkit configuration directory.
• Monitoring Interval (TKIT_MONITORING_INTERVAL)
This parameter specifies the time interval, in seconds, between two successive monitoring
verifications to make sure that the application services are up and running. This indicates how
frequently the application must be monitored.
NOTE: In Linux, you can specify the monitoring interval in microseconds. For this, you must
modify monitor_function of the tkit_module.sh script to use usleep (currently supported
only in Linux) instead of sleep.
• Monitoring Criteria (TKIT_MONITORING_TYPE/TKIT_MONITORING_ELEMENT)
The variable TKIT_MONITORING_TYPE specifies how the application is to be monitored. You
can set TKIT_MONITORING_TYPE to one of the following values, or specify an appropriate
value based on your own implementation:
◦ PID File (pid_file)
Some applications store the process ID in a file. For such applications, you can choose
the monitoring criteria (TKIT_MONITORING_TYPE) as “pid_file” (the location of the PID
file is to be assigned to the variable, TKIT_MONITORING_ELEMENT). In this case, the
Toolkit will monitor the process corresponding to the process ID stored in this file. The
name of this process must be assigned to the variable APP_SERVER_PROC.
NOTE: The APP_SERVER_PROC variable is only used in PID_FILE monitoring. For the
rest of the TKIT_MONITORING_TYPE options it is commented out.
◦ Monitoring Process Names (process_monitor)
You can choose to monitor a process by name by setting the variable
TKIT_MONITORING_TYPE to the “process_monitor”. If multiple processes must be
monitored for a single application, list all the processes by name in the
TKIT_MONITORING_ELEMENT.
◦ Monitoring Port (port_monitor)
Some applications are monitored based on the port to which they listen. You may choose
to monitor a port by setting the variable TKIT_MONITORING_TYPE to the “port_monitor”.
An example of this type of application is the Tomcat web server. For these types of
applications, you must set the port number to the variable, TKIT_MONITORING_ELEMENT.
Configuring Toolkits 11