Adding the NiagaraNetworkSystemIndexSource to the SystemIndexService on the
Supervisor triggers a new NiagaraSystemIndexDeviceExt, named System Indexer, to be added to all
Niagara stations in the NiagaraNetwork of the
Supervisor station.
As of
Niagara 4.13, you can also add and configure individual index imports against reachable stations. Similar to the NiagaraSystemIndexDeviceExt mixin, a ReachableStationSystemIndexDeviceExt, also named System Indexer, is automatically added as a mixin under any reachable station components. Therefore, you can follow similar steps to add
a NiagaraSystemIndexImport to that location for setting up an individual index import from a particular reachable station.
NOTE: If using the SystemDbService from the Typical configuration folder in the niagaraSystemIndex palette, it is already configured
with the NiagaraNetworkSystemIndexSource and so, the SystemIndexer device extension will already be added on any subordinate
stations.
For cases where you have a particular JACE on which you want to run a different indexing operation, possibly using a select set of index queries, the SystemIndexer
device extension can be a container for a NiagaraSystemIndexImport. The added (and enabled) NiagaraSystemIndexImport takes precedence over the Global Niagara Network Indexer because only one system indexer is allowed to run at any given time.
Perform the following steps:
On completion of the indexing operation,
NiagaraSystemIndexImport component pulls the indexed entity data from the remote
Niagara station to the
Supervisor, putting the data into the
Supervisor’s SystemDb.
CAUTION: Indexing a database is a memory- and CPU-intensive operation that affects the availability of your SystemDb and remote stations.
Do not configure a re-index to occur too often so your SystemDb and remote stations can maintain availability throughout the
day. If your SystemDb is indexed frequently, query performance degrades.