Key differences between Historian for Windows and Historian for Linux
The following table provides a list of the key differences between Historian for Windows and Historian for Linux:
Feature | Historian for Linux | Historian for Windows |
---|---|---|
Predix Time series style REST APIs | Yes | No |
Tuner (for the configuring Historian database) | Yes | No |
Array datatypes | No | Yes |
User-defined datatypes (custom structure) | No | Yes |
Enumeration datatype | No | Yes |
Collector redundancy | No | Yes |
Alarm and Event Archiver | No | Yes |
Diagnostic Manager for detecting faulty collectors and clients | No | Yes |
Proficy common licensing | No | Yes |
Expose data as per OPCHDA server standards | No | Yes |
Mirroring | No | Yes |
Alerts and messages are not verbal | No | Yes |
Collector portfolio of Historian for Windows and Historian for Linux
Important: All collectors in Historian for Windows can connect to the Historian for Linux database and vice versa. The following table provides a list of collectors that run on Windows and/or Linux operating systems.
Collectors | Linux Host | Microsoft Windows Host |
---|---|---|
OPCUA collector | Yes | Yes |
Server-to-Server collector | Yes | Yes |
Server-to-Cloud collector | Yes | Yes |
MQTT collector | Yes | Yes |
Windows Performance collector | Not applicable | Yes |
OPC collector | No | Yes |
OPC Historical Data Access collector | No | Yes |
Calculation collector | No | Yes |
OSI PI collector | No | Yes |
iFIX collector | No | Yes |
CygNet collector | No | Yes |
Wonderware (Schneider Electric) collector | No | Yes |
File collector | No | Yes |
Clients that cannot run on Linux Host
Important: Clients listed below can connect to Linux Historian database and operate but they cannot run on Linux Host.
-
Historian Administrator (VB admin console)
-
ihSQL client
-
Excel add-in
-
Trend client