Running Watchdog

To use the Watchdog tool:

1. Make sure that the <PPM_Home> directory contains the GC log file.

2. Navigate to <PPM_Home>/utilities/watchdog/conf directory, and open the watchdog.properties file.

3. Enter the values for the parameters listed in the following table.

   Name	Description	Required	Default
   gclog_filename	Name of the GC log file. The file name is based on the name provided during the kStart.sh run after the -Xloggc:gclog flag.	Yes	N/A
   memory_threshold	Memory threshold set in MB	Yes	300
   enable_email_notification	Enable email notification	No	true
   enable_thread_dump	Enable thread dump	No	true
   smtp_host	Host name of the SMTP server	Yes, if email notification is enabled	N/A
   sender_addr	Sender email address	Yes, if email notification is enabled	N/A
   recipients_addr	Specifies email recipients addresses. Use commas to separate multiple addresses.	Yes, if email notification is enabled	N/A
   node_name	PPM Server name		Kintana
   debug	Enables debugging		false
   use_jmx	Specifies the use of JMX to retrieve the thread dump. To use this option, start the PPM Server with the following system properties: -Dcom.sun.management.jmxremote.port=5001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management. jmxremote.authenticate=false	No	false
   jmx_output_filename	If you do not want the JMX thread dump saved in the server log, use this parameter to specify a different file name (full directory path).	No
   jmx_url	Specifies the URL used to access the PPM Server through JMX. Use the following format: /jndi/rmi://localhost:5001/jmxrmi	No
   mem_used_after_gc_position_index	Indicates the number to select as the memory used after a full garbage collection in a Full GC record.	No	9
   monitored_gc_record_indicator	Indicates the text string to use to identify the full GC record in the GC log.	No	Full GC

4. Find out the Java process ID of the PPM Server you want to monitor, and then run the following:

   sh ./kWatchdog.sh pid