HP-UX Workload Manager User's Guide

WLM quick start: the essentials for using WLM
How to put an application under WLM control
Chapter 2 83
Application records: Workload separation by binary
name
One mechanism for separating workloads is the apps statement. This
statement simply names a particular application binary and the group in
which it should be placed. You can specify multiple binary-workload
group combinations, separated by commas, in a single apps statement.
In the following prm structure, the apps statement causes the PRM
application manager to place any newly running
/opt/hpws/apache/bin/httpd executables in the group apache_grp.
prm {
groups = OTHERS : 1,
servers_grp : 2,
apache_grp : 3;
apps = apache_grp : /opt/hpws/apache/bin/httpd;
}
For more information on setting up application records, see “Assigning
applications to workload groups (optional)” on page 166.
NOTE on polling: It is important to realize that the process is not placed
in the workload group immediately after starting. Rather, the PRM
application manager periodically polls for newly started processes that
match records in the apps statement. Each matched process is placed in
its designated workload group. For more information, see the section
“Management of applications” on page 454.
User records: Workload separation by process owner
UID
You can place processes in workload groups according to the UIDs of the
process owners. You specify your user-workload group mapping in the
users statement. Here is an example:
prm {
groups = OTHERS : 1,
testers : 2,
coders : 3,
surfers : 4;
users = moe : coders surfers,