HP OpenView Operations Administrator's Reference - filibeto.org

Installing and Updating the OVO Configuration on the Managed Nodes
Distributing Scripts and Programs to the Managed Nodes
The entire directory contents are installed on each specified node,
unless if you are using Selective Distribution feature to distribute
only specified user-selected files to a particular managed node.
For more information, see “Selective Distribution of User-selected
Files to Managed Nodes” on page 209.
❏ Customized Binaries
If you need a certain binary to be present only on specific systems,
transfer the file manually. Do not put the file in the default directory
on the managed nodes. The contents of this directory are erased each
time the binaries are distributed.
For example, do not put customized commands in the following
directory:
/opt/OV/bin/OpC/cmds
❏ Customized Scripts
Specify the full path name of the customized script in the OVO
configuration. Or make sure the file is available through the $PATH
settings of the executing user on the managed node.
For example, a customized script to determine running processes
might look like one the following:
/name/opc_op/scripts/my_ps
my_ps
You can call this script as an application on the Application Desktop
or as a broadcast command.
In this example, the $PATH variable of the executing user on the
managed node must contain the following:
/name/opc_op/scripts.
❏ Distribution Manager
If many distribution requests are handled by the distribution
manager at the same time, other OVO services (for example, the
message manager) can be slowed down. If other OVO services slow
down, some managed nodes might not be able to receive data because
the distribution manager is too busy. It the distribution manager is
busy, a warning message is displayed.
Chapter 3 205