Edit the configuration text file

By editing a configuration text file, you can insert new objects into the database, modify existing objects, and delete existing objects. For example, you can add 10 new engineering units simply by adding 10 lines under the Engineering Unit entity line and then importing the configuration file into the AVEVA Historian. You can also ignore any changes to existing objects by skipping portions of the text file when importing.

Important: The order in which entities appear in the text file is important to ensure successful importing of the file. For example, if an analog tag is defined in the file, and the tag requires a new engineering unit, the new engineering unit should appear in the text file before the analog tag. The Historian Database Export/Import Utility scans the file once from top to bottom and makes no attempt at resolving ordering conflicts. As a general rule, the following order of entities in the text file should be maintained: IDAS, IOServer, Topics, System Parameter, Storage Location, EngineeringUnits, Messages, AnalogTags, DiscreteTags, StringTags, EventTags, SnapshotTags, SummaryOperations, SummaryTags, ReplicationSchedules, Replication Servers, Replication Groups, Replication Tag Entities, TagExtendedPropertyNames, and TagExtendedPropertyValues.

The following is an example of a configuration text file. All values must be separated by a tab stop.