wlmrcvdc(1M)wlmrcvdc(1M)NAMEwlmrcvdc - forward metric data to the HP-UX WLM daemon
SYNOPSIS
user] group] [ command [arg ...]]
DESCRIPTION
collects metric data from up to two rendezvous points and forwards the
data to the HP-UX WLM daemon. Two types of rendezvous points are sup‐
ported:
· Command pipe
· FIFO file
always creates a FIFO file to be fed metric data by executions of wlm‐
send(1M). If a command is also specified, starts command in the back‐
ground and reads metric values from its standard output. If command
exits with status 0, will continue running using the FIFO file ren‐
dezvous point; otherwise, will exit with error.
If you use both a command pipe and a FIFO file to send the values of a
single metric to WLM, be aware that the WLM daemon checks for new met‐
ric values once every WLM interval, and that the daemon uses only the
last value sent during this interval. This value may have come from the
command pipe or the FIFO, depending on which one was updated more
recently.
Specify as the value for a keyword in a metric structure in the HP-UX
WLM configuration file, as shown in the "EXAMPLES" section below.
Combine and to provide a script's interface to the HP-UX WLM daemon.
Use in the script to send data to the FIFO file rendezvous point, then
specify in the configuration file to pick the data up.
OPTIONS
Displays usage information and exits. This option overrides
all other options.
Displays version information and exits.
This option overrides all other options except
Sets the user (owner) of the FIFO file to
user (symbolic or numeric) and gives user write permission on the
rendezvous point. If command is specified, this option also sets
the owner of the command process to user. By default, user is
root.
Sets the UNIX group of the FIFO file to
group (symbolic or numeric) and gives group write permission on
the rendezvous point. If command is specified, this option also
sets the UNIX group of the command process to group. By default,
group is bin.
Instructs
to start command with the specified arguments in the background
and use its standard output as a second rendezvous point.
NOTE: The HP-UX WLM daemon discards the stderr of command. How‐
ever, using the tunable, you can redirect stderr to a file of your
choosing. For more information, see the wlmconf(4) manpage.
Use the full path for command unless you are using one of the com‐
mands described below.
Although you are able to use other commands, HP-UX WLM provides a
number of commands to be used in this context:
Retrieves data for applications defined in the GlancePlus file
/var/opt/perf/parm. For more information, see
glance_app(1M).
Retrieves a global (system) metric. For more information, see
glance_gbl(1M).
Retrieves general PRM data and PRM data for specific workload
groups (also
known as PRM groups). For more information, see
glance_prm(1M).
Retrieves PRM data regarding logical volumes. For more informa‐
tion, see
glance_prm_byvg(1M).
Retrieves data on ARM transactions for applications registered
through the
ARM API function For more information, see glance_tt(1M).
Checks on the status of a Serviceguard package. For more informa‐
tion, see
sg_pkg_active(1M).
Measures the response time for fetching a URL using the Apache
tool. You can use this command with the WLM Apache Toolkit
(ApacheTK) to manage your Apache-based workloads. For more
information, see time_url_fetch(1M) and /opt/wlm/tool‐
kits/apache/doc/apache_wlm_howto.html.
Helps manage the duration of processes in a workload group. For
more
information, see wlmdurdc(1M).
Produces an SQL value or an execution time (walltime) that results
from
executing SQL statements against an Oracle instance. For
more information, see wlmoradc(1M).
Retrieves metrics on BEA WebLogic Server instances. You can use
this
command with the WLM BEA WebLogic Server Toolkit (WebLog‐
icTK) to manage your WebLogic workloads. For more informa‐
tion, see wlmwlsdc(1M) and /opt/wlm/tool‐
kits/weblogic/doc/weblogic_wlm_howto.html.
METRIC VALUE FORMAT
accepts any unitless integer or floating-point number. Each metric
value must be separated by a space, tab, or newline. For example, a
response time of five seconds could be sent as "5" or "5.0", but not as
"5s" or "5 seconds".
EXAMPLES
Example #1 (Command pipe)
Create an instance of to forward values from "ordercounter" to the HP-
UX WLM daemon on behalf of metric "order_cnt". Program "ordercounter"
serves as a data collector, writing values on its stdout:
tune order_cnt {
coll_argv = wlmrcvdc /opt/books/ordercounter;
...
}
In addition to program "ordercounter", could be used to forward data to
metric "order_cnt".
Example #2 (Command pipe)
This example shows collection of average wall time for a frequently
occurring transaction in a busy application. The application registered
using the name "Transaction Application". The type of transaction being
measured is named "Insert".
# Keep average response time within acceptable limit.
slo tran_slo {
pri = 5;
mincpu = 10;
maxcpu = 75;
entity = PRM group tran_grp;
goal = metric tran_time < 3.0;
}
# Report average response time for Insert transactions.
tune tran_time {
coll_argv = wlmrcvdc
glance_tt TT_WALL_TIME_PER_TRAN
"Transaction Application"
Insert;
}
In addition to using "glance_tt", could be used to forward data
to metric "tran_time".
Example #3 (FIFO file only)
At startup, create an instance of to forward values from the
"resp_time" FIFO rendezvous point to the HP-UX WLM daemon on behalf of
all interested SLOs. The rendezvous point will be owned by user
"admin" of group "sys":
tune resp_time {
coll_argv = wlmrcvdc-u admin -g sys;
}
Use in a data collector script to forward values to the established
FIFO rendezvous point.
See wlmconf(4) for more details on establishing SLO-specific data col‐
lectors.
Example #4 (Managing Oracle)
This example gets the number of connected users for the Oracle instance
named instance1. This number is obtained by an SQL SELECT in the con‐
figuration file user_cnt.oradc.
tune user_cnt {
coll_argv =
wlmrcvdc
wlmoradc
--configfile /opt/wlm/toolkits/oracle/config/user_cnt.oradc
--instance instance1;
}
The associated SLO could increase the CPU resources for the instance's
workload group when the number of connected users passes a certain
threshold. Alternatively, using the keyword, the associated SLO could
grant the instance's workload group a certain number of CPU shares for
each connected user.
RETURN VALUE
returns exit status if no errors occur, or if there are errors. Diag‐
nostic messages are logged to the file /var/opt/wlm/msglog.
AUTHOR
was developed by HP.
FEEDBACK
If you would like to comment on the current HP-UX WLM functionality or
make suggestions for future releases, please send email to:
wlmfeedback@rsn.hp.com
SEE ALSOwlmsend(1M), glance_app(1M), glance_gbl(1M), glance_prm(1M),
glance_prm_byvg(1M), glance_tt(1M), sg_pkg_active(1M),
time_url_fetch(1M), wlmdurdc(1M), wlmoradc(1M), wlmwlsdc(1M), wlm‐
conf(4), wlm(5)
HP-UX Workload Manager User's Guide (/opt/wlm/share/doc/WLMug.pdf)
HP-UX Workload Manager Toolkits User's Guide (/opt/wlm/tool‐
kits/doc/WLMTKug.pdf)
"Writing a Better WLM Data Collector" white paper
(/opt/wlm/share/doc/howto/perfmon.html)
HP-UX Workload Manager homepage (http://www.hp.com/go/wlm)
wlmrcvdc(1M)
