Application Server historization components

To save your process data to a historical database, you must install the Historian Server. An Historian Server database can be installed on any computer outside the Galaxy, but on the same network. In a production environment, the Historian should be installed on a dedicated computer without other System Platform products running on it.

The following figure shows the major System Platform components to save process data from a production device to the Historian.

A single Historian installation can receive historical data from a single Galaxy. A push model is used to send and save new historical updates to Historian. Each system object Engine (Platform, AppEngine, and ViewEngine) includes a historian feature that sends all history updates for all hosted objects to the historian. The historian feature receives the history updates from objects on the same engine only. All AppEngine and ViewEngine objects include an attribute to specify the node name of the computer hosting Historian.

Note: A WebViewEngine does not send any data to the Historian.

The figure shows a single Historian. This may be a common configuration, but other Application Server configurations support multiple Historian databases for a Galaxy. However, each Engine object only sends its historical data to one Historian.

There is a one-to-one relationship between a historical object attribute and a tag in Historian.