Monitoring

AVEVA Enterprise SCADA comprises a series of services, and each service can have any number of processes working together. Each service can operate independently, or in conjunction with other services in a layered, hierarchical fashion.

To de-couple the core AVEVA Enterprise SCADA service infrastructure from any individual service implementation, the infrastructure executes scripts provided by each service. The service scripts perform any specialized tasks of starting, shutting down, and failing over that are unique to the individual service. In this way, the Common service infrastructure can be reused to manage an application or a group of logically connected applications. The application Developer(s) can depend on this infrastructure for the framework that is expected by all AVEVA Enterprise SCADA server software.

The AVEVA Enterprise SCADA Service infrastructure provides a comprehensive framework that any service can leverage, including:

• Process Monitoring.

• Generic Computer Health Monitoring (Disk, Network, Physical Memory, and so forth).

• A generic user interface for starting, stopping and monitoring the service.

• The capability for a service to operate in a redundant fashion on two separate hosts; also referred to as an Arbitrated Service.

• Middleware (PubSub, Microsoft SQL, Business Components).

• Utility libraries.

  

Service startup sequence:

• dnaService starts the dnaHealthMonitor and processMonitor processes that monitor the health of all processes that are registered as members of the service.

• dnaService executes the startup.csc script within %DnaInstallRoot%\<silo>\scripts\<serviceName>.

• If the service is arbitrated, dnaService starts the arbMonitor process.

• Once started, the Operating System requests any further service actions (particularly service shutdowns) by sending a request to the dnaService process.

Service shutdown sequence:

• If the service is arbitrated, the service state is set to FAIL.

• dnaService asks the processMonitor to kill all processes that are associated with the service.

• dnaService then runs the shutdown.csc script within %DnaInstallRoot%\<silo>\scripts\<serviceName>.

  Note: Each AVEVA Enterprise SCADA Service starts an instance of dnaService, and the associated processes.