Process monitoring infrastructure

Process monitoring functionality involves monitoring the state of individual processes that are considered members of a specific service.

Each monitored process uses the Process Monitoring Application Programming Interface (API). This API allows a process to check in, or register interest with the AVEVA Enterprise SCADA Process Monitor.

When a process checks in, it can identify a series of characteristics about the kind of monitoring that should be performed. For example:

• Whether the Process Monitor should expect the given process to periodically check in, and if so, how frequent the Process Monitor should expect the updates to occur.

• Whether the process is considered critical.

  

When a process does not check in to the Process Monitor within the established expected frequency, the lack of an update leads to the death of the process. It will be considered to be in a failure state. The failure of a process that is considered critical results in the Process Monitor asking the service to failover to a standby server if one is available.

The Process Monitor API uses the Process Monitor Cache shared memory segment to ensure Process Monitor API operations are fast. This cache is secured using the Kerberos authentication. Only a member of the DNA Apps security group may connect to this shared memory segment.

When a process does not check in to the Process Monitor within the established expected frequency, the lack of an update leads to the death of the process. It will be considered to be in a failure state. The failure of a process that is considered critical results in the Process Monitor asking the service to failover to a standby server if one is available.

Note: Each AVEVA Enterprise SCADA Service starts an instance of the Process Monitor.