IDAS configuration

During normal operation, when the Historian is started, it configures an IDAS by sending it information about the tags (including their data sources) for which the IDAS is to acquire data. When the Historian Storage subsystem is ready to accept data, IDAS automatically connects to its data sources, starts acquiring data, and sends the data to the Historian Storage subsystem for historization.

The primary purpose for IDAS configuration files is to minimize network traffic and provide information for IDASs configured for autonomous startup. For more information on autonomous startup, see IDAS autonomous startup.

The IDAS saves configuration information to a file on the local hard drive in the following folder of the IDAS computer: ProgramData\ArchestrA\Historian\IDAS\Configurations.

The IDAS configuration file is named as follows:

idascfg_SERVERNAME_IDASKEY.dat

where:

• SERVERNAME is the NetBIOS name of the Historian computer

• IDASKEY is the value of the IODriverKey column for the IDAS in the Runtime database

You can change the IDAS configuration from the Operations Control Management Console. The Historian dynamically reconfigures itself. If the IDAS is on a remote computer, the Historian sends the updated configuration information to the IDAS. The IDAS reconfigures itself and updates the local configuration file. The IDAS continuously acquires and sends data during the reconfiguration process. The Historian saves its copy of the updated IDAS configuration file in the following folder of the Historian computer: ProgramData\ArchestrA\Historian\Configuration\IDAS Configurations.

After a successfully configuring IDAS, a copy of the IDAS configuration file is stored on the Historian computer. The IDAS configuration file stored on the IDAS computer is identical.

Important: IDAS configuration files have a proprietary binary format. Do not modify these files.

If there is more than one autonomous configuration file on the IDAS computer (for example, if you deleted an IDAS on a node while it was disconnected and then added one again), only the newest file is used. A warning is logged on the IDAS computer. For more information on autonomous startup, see IDAS autonomous startup.