About Configuration Hub

The Configuration Hub application allows you to manage the Historian models, Historian systems, and their components.

Advantages of Using Configuration Hub:
  • Creating a Historian model: You can create and manage object models, which is a hierarchical classification of objects. A model contains object types, variables, and instances.
  • A single application that enables you to manage multiple Historian systems: A Historian system is a network of Historian servers that collect, store, and retrieve data related to tags, alarms, and events.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. For information on setting up a stand-alone Historian system, refer to About Setting up a Stand-Alone Historian System.
  • 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. For information on setting up a horizontally scalable system, refer to About Setting up a Horizontally Scalable System.
Limitations
  • 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, or modify an instance of offline collectors. In addition, you cannot compress network messages.
  • 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.
  • If the primary server is down, you cannot add tags using a distributed node because the Configuration Manager service is down.
  • Using Configuration Hub, you cannot create enumerated sets and user-defined types (UDT) for tags. You can, however, use the ones created in Historian Administrator.
  • Using Configuration Hub, you cannot define a calculation formula for a tag for a Calculation collector. You can, however, define a calculation formula using Historian Administrator or other Web-based Clients.
  • Using Configuration Hub, you cannot configure an iFIX Alarms and Events collector and an OPC Classic Alarms and Events collector. However, you can configure them using Historian Administrator.
  • Using Configuration Hub, you cannot configure a HAB collector. You can, however, configure it using XML files.
  • When browsing for tags hierarchically, if a folder contains subfolders, the tags in the parent folder do not appear. You can, however, access these tags using Historian Administrator.