Table of Contents
Advertisement
An Overview of ITO Processes
Understanding ITO Processes
For more information on how the processes communicate with one
another and what each process does, see "Management Server Processes"
on page 356 and "Managed Node Processes" on page 360.
Management Server Processes
The following list gives details of which processes run on the ITO
management server, what each process does, and, where necessary, how
the processes interact:
The ITO GUI logon program is used by the ITO
opc
administrator and by ITO operators and calls either
opcuiadm and opcuiopadm or opcuiop according to
the User Name specified.
The action manager feeds the action agents with
opcactm
automatic and operator-initiated actions, scheduled
actions, application-startup and broadcasting
information via the control agent. In addition,
external instruction texts are determined using this
mechanism.
The request sender informs the control agents to
ovoareqsdr
start, stop, or update their local ITO agents. The
request sender is also responsible for ITO's self-
monitoring of ITO manager services, and for the
heartbeat-polling of the managed nodes.
The control manager starts and stops all other ITO
opcctlm
manager processes, performs all licence checking, and
controls the ITO database maintenance functionality.
The display manager serves the ITO Motif-based
opcdispm
GUI. The display manager also feeds the action
manager with operator-initiated actions, application
startup (not requiring a separate terminal) or
broadcasting information issued by the ITO operator.
Several ITO user GUIs may be active at the same time,
but only one Motif-based GUI can be run for each ITO
operator.
The distribution manager distributes node-specific
opcdistm
configurations to managed nodes in response to
requests by the distribution agent (opcdista). Sub-
processes (opctts) are forked for each parallel
356
Chapter 9
Advertisement
Table of Contents
Troubleshooting
