Configure a register

Registers for Data Capture are defined under InfoInterface/Data Sources in general ISM extensions, as shown in the following figure.

Registers can be nested in sub folders for organizational purposes and to inherit common settings (which may be overridden) but cannot be moved once used as this defines a new register.

Minimum register definition

A register must at minimum define the following options:

• A category such as Tags, which groups data from different interfaces into a set.

• A RegisterType such as Primary which defines how a register should be read.

• An IDColumn or IDExpression, which defines how to identify captured records.

• A Columns folder with one or more Column entries that are of interest.

The following figure shows how register defines the various options.

Register columns

Registers must define at least one column, which is mapped to an actual attribute during interpret phase using Corresponding identifiers mapping, or by finding an attribute with the same ID. If there is no corresponding attribute to map to, the captured data is still captured, but is not mapped (so is ignored unless mapping rules are updated).

The following figure shows the register columns.

For more information about register configuration options, refer Register options.