Historian Installation Workflow
- Design your system architecture.
Decide what collectors to instantiate on which nodes, which computers to designate as the Historian server and Historian Administrator, whether or not they will be web-based, and how much memory and disk space you can assign to buffers and archives. Record the computer names of each node.
- Ensure that data sources are installed.
- Set up your Historian environment.
- On the server node, launch the installer, select Install Historian, and follow the on-page instructions to install Historian on a single server on in a distributed environment.
- Activate your product license.
- Install the collectors.
- Restart your computer if prompted to do so.
- As needed, install Web-based Clients.
- Perform post install setup for MTLS features, by installing certificates. For more information, refer to Overview of certificate-based security.
-
For the Windows-based Historian Administrator clients, start the Administrator from Historian Startup Group.
When the home page for Historian Administrator appears, you are ready to set up archives, collectors, and tags in the Data Store Maintenance, Collector Maintenance, and Tag Maintenance pages.
| Installation Option | When to Install |
|---|---|
| Historian Server | Installing the Historian server is mandatory to work with
Historian. If you want to use Web-based Clients, you must
provide the Proficy Authentication server details while
installing the Historian server. When you install the
Historian server, the following components are installed as
well:
|
| Alarms and Events | Install Alarms and Events if you want to retrieve and store alarms and events data from any OPC-compliant alarms and events server using the OPC Classic Alarms and Events collector. |
| Collectors | Installing collectors is mandatory to collect and store data
in Historian. When you install collectors, all the collectors and the Remote Management Agents are installed. You must then create instances of each collector and manage them using Configuration Hub. When you install collectors,
if iFIX/CIMPLICITY are installed on the same machine,
instances of the following collectors are created
automatically:
|
| Client Tools | Install Client Tools if you want the following components:
|
| Web-based Clients | Install Web-based Clients if you want to manage Historian
administrative tasks and analyze the data using components such
as Configuration
Hub, the Web Admin
console, Trend
Client, and REST APIs. To use Web-based Clients, you need Proficy Authentication (UAA server) to handle user authentication. It provides identity-based security for applications and APIs. It supports open standards for authentication and authorization, including Oauth2. During the Web-based Clients installation, you can choose to install a Proficy Authentication instance and Configuration Hub, or you can use existing ones. |
| Historian Remote Management Agents | Remote Management Agents (RMA) include Remote Collector Manager, which is used to manage collectors remotely. RMA is installed automatically when you install collectors. If, however, you are using RMA version 8.1, and you want to upgrade only RMA (and not the collectors), use this option. |
| Excel Add-in for Historian | Install Excel Add-in for Historian make bulk changes to tag parameters using Excel, and then import it to Historian. You can also perform mathematical, retrieve selected data, generate reports and charts, and so on. |
| Excel Add-in for Operations Hub | Install Excel Add-in for Operations Hub if you want to query historical data of objects and object types defined in Operations Hub. |
| ETL Tools | Install the Historian Extract, Transform, and Load (ETL) tools if you want to transfer data where there is limited internet connectivity. |
| The OPC UA HDA Server | Install the OPC UA HDA server if you want to use Historian as an OPC UA HDA server. You can then connect any OPC UA HDA clients with the server. |
| Standalone Help | Install Standalone Help to access the Historian product documentation offline. |