HP-UX Workload Manager User's Guide

Advanced WLM usage: Using performance metrics
Supplying data to WLM
Appendix H488
ARM transaction data
For information on:
• How to get transaction data for an application that is already
instrumented with ARM API calls to WLM
• How to instrument an application with ARM API calls
see “Sending ARM transaction data from a modified C program” on
page 504.
For information on how to simulate transactions, see “Sending ARM
transaction data from a script with simulated transactions” on page 509.
GlancePlus application data
You can define GlancePlus applications in the /var/opt/perf/parm file.
Defining applications helps you see what is going on within a WLM
workload group. You can also configure your WLM workload groups to be
considered “applications.” For more information, see “Integrating with
OpenView Performance Agent (OVPA) / OpenView Performance
Manager (OVPM)” on page 413.
The following example shows an application definition for Oracle
database software:
application = Oracle
file = ora*, sqldba, sqlplus, tnslsnr, lsnrctl
By creating such an entry in the parm file, we can access metrics for all
Oracle and associated processes on the system.
Examples of GlancePlus application metrics are:
APP_ACTIVE_PROC
The number of processes in a GlancePlus application
that are competing for the CPU resources.
APP_ALIVE_PROC
The number of processes that exist in a GlancePlus
application.
APP_CPU_TOTAL_UTIL