Add and Configure an OPC Classic Alarms and Events Collector
About this task
You can create an OPC Alarms and Events collector only for an on-premises Historian server, not for a cloud destination.
This topic describes how to add a collector instance using Configuration Hub. You can also add a collector instance using the RemoteCollectorConfigurator utility, which does not require you to install Web-based Clients.Procedure
- Access Configuration Hub.
-
In the NAVIGATION section, under the Configuration Hub
plugin for Historian, select Collectors.
A list of collectors in the default system appears.
-
In the upper-right corner of the main section, select
.
The Add Collector Instance: <system name> window appears, displaying the Collector Selection section. The MACHINE NAME field contains a list of machines on which you have installed collectors. - In the MACHINE NAME field, select the machine in which you want to add a collector instance.
-
In the COLLECTOR TYPE field, select OPC
Alarms and Events Collector, and then select Get
Details.
The INSTALLATION DRIVE and DATA DIRECTORY fields are disabled and populated.
-
Select Next.
The Source Configuration section appears.
- In the OPC A&E SERVER field, enter the host name or IP address of the OPC server from which you want to collect alarms and events data.
-
Select Next.
The Destination Configuration section appears. Under CHOOSE DESTINATION, the Historian Server option is selected by default; the other options are disabled. In addition, the DESTINATION HISTORIAN SERVER field is disabled and populated with the value you selected in the MACHINE NAME field in the Collector Selection section.
-
If you created security groups or enabled a strict client/collector
authentication, enter the USERNAME and
PASSWORD of the on-premises Historian server that you
created during the installation of the collector.
If you entered the USERNAMEand PASSWORD, select Test Connection. This will help you to test if the Historian server that you are trying to connect is valid or if the credentials that you entered are valid.
-
Select Next.
The Collector Initiation section appears.
-
If needed, modify the value in the COLLECTOR NAME
field.
The value that you enter:
- Must be unique.
- Must not exceed 15 characters.
- Must not contain a space.
- Must not contain special characters except a hyphen, period, and an underscore.
-
In the RUNNING MODE field, select one of the following
options.
- Service - Local System Account: Select this option if you want to run the collector as a Windows service using the credentials of the local user (that is, the currently logged-in user). If you select this option, the USERNAME and PASSWORD fields are disabled.
- Service Under Specific User Account: Select this
option if you want to run the collector as a Windows service using a
specific user account. If you select this option, you must enter values
in the USERNAME and
PASSWORD fields. If you have enabled the Enforce Strict Collector Authentication option in Historian Administrator, you must provide the credentials of a user who is added to at least one of the following security groups:
- iH Security Admins
- iH Collector Admins
- iH Tag Admins
You can also configure the collector to start automatically when you start the computer.
-
Select Add.
The collector instance is added. The fields specific to the collector section appear in the DETAILS section.
-
In the COLLECTOR SPECIFIC CONFIGURATION section, configure
the values as described in the following table.
Field Description MTLS Security Indicates whether you want to use Mutual TLS (MTLS) protocol to enforce a secure and strong authentication mechanism. MTLS Data Encryption Indicates whether you want to encrypt the data that the collector shares to the data archiver (DA). For more information on how to enable MTLS Security, refer to Enable MTLS Security. - As needed, enter values in the other sections common to all collectors.
-
In the upper-left corner of the page, select Save.
The changes to the collector instance are saved. - If needed, restart the collector.