Application Object Server

An Application Object Server (AOS) node is a run-time platform used for hosting run-time objects (instances) in a deployed Galaxy.

The Application Object Server (AOS) node provides the run-time resources for AppEngines, Areas, AutomationObjects, and DeviceIntegration (DI) Objects. The AOS node requires a Platform to be deployed. The OPCClient objects are generally used for device integration.

AOS functionality can be combined with a visualization node, depending on the process requirements and system capabilities. A distributed local network topology takes advantage of this type of configuration to provide flexibility to the system.

There is in interplay between the number of AppEngines, scan rate, and I/O count that affect how an AOS node should be sized. No more than two AppEngines (primary and backup) should be deployed to each logical core on an AOS node. Faster scan rates will result in a lower I/O threshold. In other words, the higher scan rate, the lower the I/O count that can be supported on the AOS node.

The following are the core components of an AOS node:

• Bootstrap

• PCS Runtime

• System Monitor

In addition to the components listed above, the following AVEVA/System Platform components and applications are also installed:

• Historian Client

• Operations Control Management Console

• Operations Control Logger

• AVEVA Communications Drivers Pack

• AVEVA Application Manager

OI server functions are frequently combined on an AOS node, if the I/O load permits.