Integrating Applications As Actions; Integrating Monitoring Applications - HP -UX B6941-90001 Administrator's Reference Manual

Integrating Applications into ITO
Integrating Applications into ITO

Integrating Applications as Actions

An application or script may be configured to run as an automatic or
operator-initiated action, or a scheduled action. An automatic action is
triggered by a message received in ITO. An operator-initiated action is
merely enabled by a message received in ITO; it is executed by the
operator. Operator-initiated actions may also be triggered by the
administrator, via the message browser. Scheduled actions are
configured by the administrator and execute a routine task at a
configured time. These actions are always performed by the ITO action
agent, which operates as root on UNIX systems, as AGENT.OVOPC on
MPE/iX systems, and as HP ITO Account on Windows NT systems. Note
that the action must be available on the managed node.
NOTE Note that HP ITO Account is part of the Administrator, Domain
Administrator and User Administrator groups. If an action is prohibited
for one of these groups, the HP ITO Account will not be able to perform
that action.
The application must be accessible via the root's $PATH settings on
UNIX systems, or the path must be fully qualified on the corresponding
message condition configuration window.
You can also distribute simple and widely used applications via ITO to
the managed node as explained in "Distributing the ITO Agent
Configuration to the Managed Nodes" on page 305.

Integrating Monitoring Applications

Applications can be used for monitoring purposes if they deliver the
monitored object status using the opcmon(1) command or opcmon(3)
API.
The monitoring application must be accessible via the root's $PATH
settings on UNIX systems, or the path must be fully qualified on the
corresponding monitor configuration window. Note that the application
must be available on the managed node.
You can also distribute simple and widely used monitoring applications
via ITO to the managed node as explained in "Distributing the ITO
Agent Configuration to the Managed Nodes" on page 305.
Chapter 7 325