Processes
Processes are programs that are run by a process agent on the same workstation, within a process control system. Processes must be defined in a service, for ease of management.
Dependent processes
The order in which applications are started can be important. You can use process control to configure processes to be dependent on each other if they are in the same service. For example, a process can be configured to start only after another process has started and completed various startup tasks.
A PA aware process communicates with the process agent. When the process reaches the point in its startup where it recognizes itself to be running, it sends a message to the process agent. When the process agent receives this message, it starts dependent processes.
Process control awareness
PaPA_AWARE process is one that is part of the process control configuration
and is aware of process control. A PaPA_AWARE process notifies the process agent
when the process reaches a ready state after the process starts and all process
control features, such as process dependencies, can be used. The following Netcool components are
PaPA_AWARE.- Process agents. One process agent can run under the control of another process agent.
- ObjectServers
- Gateways
- Probes
- Firewall Bridge
- Proxy Server
PaPA_AWARE attributes are used when the process agent starts processes
that are defined in the process agent configuration to depend on each other. If one process, for
example a probe, depends on another process, such as an ObjectServer, then the process agent delays
startup of the dependent process (for example, probe) until the process it depends on (for example,
ObjectServer) signals that it is ready and can accept connections.A PaNOT_PA_AWARE process cannot communicate with the process agent and is
unaware that it is started by the process agent. This behaviour would be true for all non-Netcool
process that are configured to run under process agent control. For example, the Tivoli Netcool/OMNIbus desktop is
PaNOT_PA_AWARE.