HistorianData Retrieval Components
Data retrieval components are used to retrieve data that is stored in the Historian server. This topic provides a list of these components.
- Historian Alarms and Events
- Historian Alarms and Events provides tools to collect, archive, and retrieve alarms and events data in Historian.
Refer to Historian Alarms and Events for more information.
- Historian Client Manager
- The Historian Client Manager acts as the client connection manager and message router for the system. The Client Manager will examine messages and forward them to the correct Data Archiver or to the Configuration Manager. This service is deployed only for mirrored systems.
- Historian Configuration Manager
- The Historian Configuration Manager maintains and distributes the entire System configuration. There can be multiple Historian nodes but only one Configuration Manager. This Configuration Manager node is used to store system configuration, such as tag names, collector names and Historian Node names. This service is deployed only for mirrored systems.
- UAA Tomcat Container
- An instance of Tomcat is used exclusively by Historian as an open source Java-based Web server to support the External UAA.
- Historian PostgreSQL Database
- An instance of PostgreSQL is used exclusively by Historian to store tag names to improve searching for tags in the Trend tool and Web Admin console.
- Historian OPC Classic HDA server
- The Historian OPC Classic HDA
server reads the raw data stored in Historian and sends it to the connected OPC Classic HDA
collectors. The Historian OPC Classic HDA
server is in compliance with OPC Server HDA 1.20 standards.
Refer to the Historian OPC Classic HDA server manual for more information.
- Historian User API
- The Historian User API is intended to provide high speed read/write access to Historian data and read access to Historian tags. There is no access to alarms, events, or messages.
Use the API to develop applications in C or C++, which read and write data to the Historian server when the Historian SDK and Historian OLEDB do not meet your project requirements for performance or programming language.
Historian allows you to develop both 32-bit and 64-bit User API programs.Note: If you want to build a 32-bit User API program on a 64-bit operating system, then you need to rename the ihuapi32.lib to ihuapi.lib and include it in your program.Refer to the ihUserApi Help system for more information.
- Historian Web REST API
- Historian includes a REST API to connect your Java Web-based Clients with Historian data. Refer to the Historian REST API Reference Manual in the /Additional Documentation folder of your installation directory for more information.
- Historian SDK
- The Software Development Kit (SDK) is designed for writing Visual Basic (VB) or Visual Basic for Applications (VBA) Scripts. Using the SDK, you can develop your own scripts to perform selected repetitive or complex tasks or to make your own custom user interface. To use the SDK, create a VB/VBA project with the SDK as a project reference. Refer to the SDK Help system for more information.
- Historian Client Access API
- The Historian Client Access API is a .NET Core assembly that interacts with
Historian from any .NET Core applications. Since it works with .NET
Core, it is platform-independent - you can use it on any operating system,
such as Windows, Linux, and Mac OS.
Note: You can still use the old Client Access API, which is a .NET assembly. It is installed when you install Client Tools.
- JAVA APIs
- Most open source, quick development applications rely on JAVA as their programing language. To enable easier integration with Historian, JAVA APIs are provided. The JAVA APIs support 64-bit Windows Operating Systems.
Refer to the Historian JAVA API Reference Offline Manual in the /Additional Documentation folder of your installation directory for more information.
