PTPerformanceMonitor
Application class - PTEM_CONFIG:PTPerformanceMonitor
Before you run the PTPerformanceMonitor plug-in, ensure that the following pre-requisites are set in the monitoring system and in the monitored system:
Note:
The PTPerformanceMonitor plug-in must be run in the monitoring and in the monitored systems.
-
Perf Collator should be set to Yes (enabled) for the corresponding application server domain.
-
In the psappsrv.cfg file and the psprcs.cfg file, the EnablePPM Agent parameter should be set to 1.
-
Process scheduler domain must be up and running so that the reaper and archive jobs can be scheduled successfully.
-
In the web profile configuration, set the following:
-
In the General tab, select the EnablePPM Agent parameter.
-
In the Custom Properties tab, set the value of PPMConsole parameter to True.
If the PPMConsole parameter is not present, add the parameter. The parameter must be of Boolean type.
-
Additionally, to enable Usage Monitor as part of the performance monitor configurations, the following pre-requisites are required:
-
In the psappsrv.cfg file, the Usage Monitoring State parameter should be set to 1 or 2.
-
On the System Defaults page (PeopleTools, Performance Monitor, Administration, System Defaults), the Enable Usage Monitoring check box should be selected. Alternatively, in the PTPerformanceMonitor plug-in properties, you can set the env.usemon_sw property to 1.
Important:
After executing the PTPerformanceMonitor plug-in, clear the cache and restart the application server and Web server for the configurations to take effect.
| Property | Default Value | Description |
|---|---|---|
|
env.pm_sampling_rate |
0 |
Agent PMU sample rate (1/X). |
|
env.pm_buff_int |
0 |
Agent buffering interval (in seconds). |
|
env.pm_sample_int |
0 |
Agent event sample rate (in seconds). |
|
env.pm_ping_int |
0 |
Agent heartbeat interval (in seconds). |
|
env.pm_user_trace |
Allow performance trace. |
|
|
env.pm_max_buff |
0 |
Agent maximum buffer size (in bytes). |
|
env.pm_max_hist_age |
0 |
Retention period (in days). |
|
env.usemon_sw |
0 |
Enable usage monitoring. |
|
env.pm_max_trans_tmout |
0 |
PMU timeout (in days). |
|
env.pm_archive_mode |
Valid values for archiving:
|
|
|
env.pm_filter_level2 |
Filter level values for log documentation:
|
|
|
env.monitor_url |
Enter an URL in the following format or enter NONE. Format: http(s)://host[:port]/monitor/[site]/ If you enter NONE, the performance monitor components on the monitored system are not enabled. |
|
|
env.ppmi_user_name |
PPMI user ID. |
|
|
env.ppmi_password |
PPMI password. |
|
|
env.collator_row_limit |
Collator row limit. Use 0 for unlimited rows. |
|
|
env.ppmi_url |
PPMI URL. Format: http://host[:port]/monitor/[site]/ |
|
|
env.schedule_reaper_job |
Y |
Flag to determine whether the Reaper job needs to be scheduled. |
|
env.schedule_lookup_job |
Y |
Flag to determine whether the Lookup job needs to be scheduled. |
|
env.schedule_archive_job |
Y |
Flag to determine whether the Archive job needs to be scheduled. |
|
env.schedule_umlookup_job |
Y |
Flag to whether the Usage Monitor Lookup job needs to be scheduled. |
|
env.cluster_list |
List of performance monitor clusters. |
|
|
env.insert_cluster_urls |
N |
Flag to determine whether performance monitor clusters need to be inserted or not. |
|
env.delete_cluster_urls |
N |
Flag to determine whether performance monitor clusters need to be deleted or not. |