HP-UX Workload Manager Toolkits User's Guide

HP-UX WLM Oracle Database Toolkit: Providing Database Metrics to WLM
How do I use the metrics?
Chapter 250
In the WLM configuration file, instances are separated using the apps
keyword. In the example below, from
/opt/wlm/toolkits/oracle/config/batchuser_boost.wlm, there are four
workload groups. Processes for the instance named instance1, which are
presumably of the form ora*instance1, are placed in the workload
group Ora_grp_1. Similarly, instance2 processes are placed in
Ora_grp_2.
NOTE Starting with WLM A.03.01, WLM also allows you to define process
maps with which you can place processes in workload groups based on
your own criteria. For example, you can specify an Oracle script to gather
the processes and have them placed in a specified workload group.
prm {
groups = OTHERS : 1,
Ora_grp_1 : 2,
Ora_grp_2 : 3,
long_batch : 4;
apps = Ora_grp_1:/oracle/app/oracle/product/8.1.5/bin/oracle
"ora*instance1",
Ora_grp_1:/workload1/oltp1,
Ora_grp_2:/oracle/app/oracle/product/8.1.5/bin/oracle
"ora*instance2",
Ora_grp_2:/workload2/oltp2,
long_batch:/oracle/demo/batch/long_batch;
}
Enabling and disabling SLOs based on database
metrics
This section explains how to enable and disable SLOs based on number
of processes, number of connections, queue length, and other such
metrics.
WLM provides a mechanism to cause an SLO to be active or inactive for
a given period of time. This feature is accessed through the condition
and exception keywords, as explained in wlmconf(4). You can use time
of day, day of week, and so forth to drive a condition. Also, external
metric values can drive the conditions.