About Configuration Hub

A Historian system is a network of Historian servers that collect, store, and retrieve data related to tags, alarms, and events.

The Configuration Hub application allows you to manage the Historian systems and its components.

Advantages of Using Configuration Hub:
  • A single application that enables you to manage multiple Historian systems: You can create and manage Historian systems using Configuration Hub. In addition, you can manage collectors, data stores, and tags.
  • Horizontal scalability: You can increase the storage capacity of a Historian system by connecting multiple software entities so that they work as a single logical unit. This will improve the performance of the Historian system. The storage capacity depends on the number of Historian licenses that you have purchased.
  • High availability: You can create mirror locations in a Historian system to achieve high availability of the server. If one of the servers is not available, you can retrieve data from the remaining servers in the mirror location.
  • Ease of setting up: You can install all the collectors used in a Historian system easily by providing the required details with the help of the user-friendly interface.
Types of Historian Systems
  • Stand-Alone: In a stand-alone Historian system, there is only one Historian server. This type of system is suitable for a small-scale Historian setup.
  • Horizontally scalable: In a horizontally scalable Historian system, there are multiple Historian servers, all of which are connected to one another. This type of system is used to scale out the system horizontally. For example, if you have 5,00,000 tags in your Historian system, you can distribute them among the various servers to improve performance.
Components of a Historian System: In a Historian system, the following components are used. This list is not comprehensive. For a complete list, refer to System Components.
  • Servers: A server is a machine on which Historian is installed. It contains a location and one or more data stores. A stand-alone Historian system contains only one server, whereas a horizontally scalable one contains multiple servers.
  • Data stores: These are logical collections of tags used to store, organize, and manage tags according to your requirements. The primary use of data stores is segregating tags by data collection intervals. For example, you can put name plate or static tags (where the value rarely changes) in one data store, and put process tags in another data store. This can improve the query performance.
  • Locations: These are virtual entities in which data stores are created. They are used for storage. The following types of locations are used in a horizontally scalable Historian system:
    • Distributed location: This location is created automatically when you install a Historian mirror primary server, or when you install a Historian distributed/mirror node and add it to the primary server. You cannot modify or delete this location, or create another one.
    • Mirror location: This location is used to replicate data collected in a data store. When you create a mirror location, you add one or more servers to the group, and then create the data stores whose data you want to replicate. For example, suppose you want to create a data store for collecting the data for 100 tags, for which you want high availability. In that case, you must create a mirror location, add two or more servers to the mirror location, and then create the data store. When you do so, the data retrieved in the data store is stored in all the servers in the mirror location. If one of the servers is down, you can retrieve the data from the other servers in the group.
  • Tags: These are the parameters for which you want to store data (for example, temperature, pressure, torque).
  • Collectors: These are the applications that collect data from a data source, and send it to Historian or another destination such as Predix Time Series or an Azure IoT hub.
  • Data archiver: This is a service that indexes all the data by tag name and timestamp, and stores the result in an .iha file.
  • Clients: These are applications that retrieve data from the archive files using the Historian API.
  • If only one machine remains in a mirror location, you cannot remove it.
  • You cannot add comments, enable the debug mode, pause data collection, resume data collection, modify, or delete an instance of offline collectors. In addition, you cannot compress network messages. You can, however, add or delete the collector instance using the Collector Manager utility at a command prompt.
  • If you install Configuration Hub and the Web Admin console on the same machine, and use self-signed certificates for both of them, the login page for Configuration Hub does not appear. To prevent this issue, disable the domain security policies:
    1. Access the following URL: chrome://net-internals/#hsts
    2. In the Domain Security Policy section, in the Delete domain security policies field, enter the domain name for Configuration Hub, and then select Delete.
  • Configuration Hub is not supported in a clustered Historian environment.