Automation Manager#

The Automation Manager represents a server or dedicated computer that will be capable of running multiple Automation Controllers and multiple Automation Drivers.

How It Works#

The Automation Manager consists of two processes:

• The Automation Manager
  • Starts and monitors the processes
  • Starts and stops other processes on demand from the Automation Monitor
  • Stores and retrieves persisted data
• The Automation Monitor
  • Connects and interacts with the system
  • Processes the workload (controllers, drivers)
  • Downloads packages versions
  • Requests packages to be started and stopped
  • Updates itself
  • Creates the communication channel between controller and driver(s)

In a nutshell, the Automation Monitor process is the real responsible for the automation handling process; the Automation Manager process basically spawns/kills other processes.

The Automation Monitor has a heartbeat function that will communicate with the Controllers and Drivers at specific periods of time to ensure it is online and responding to requests. The Monitor can be configured to restart any processes in the controller or driver if they do not respond in a timely manner to the heartbeat and if a specific number of allowed failures has been reached.