The database is “pluggable”. The default selection is the InactiveSystemDb. Currently, only the OrientDb selection is available.
OrientIndex configuration components are exposed in the orientSystemDb-se module palette and allow you to manually drag and drop them under a container under the OrientSystemDb component in a running or offline station. When enabled, the OrientIndex components create orient indexes based on the configured settings and are mainly used to improve query performance for commonly queried tags. When disabled or removed, the corresponding orient index is dropped from the underlying Orient database.
The System Database stores entities, tags, and relations indexed from the

In addition to standard properties (for example, Status, Enabled, Fault Cause, Alarm Source Info, and Monitor, etc.), this component provides the following configuration properties.
| Property | Value | Description |
|---|---|---|
| System Database Type Selection | InactiveSystemDb (default), OrientDb | Indicates the type of backend database to be used. When initially installed, the default selection is “InactiveSystemDb”. This default inactive selection is intentional because when OrientDb is selected it creates a lot of files in the station protected home directory. So this default inactive selection prevents that from happening if the SystemDbService is accidentally dropped into a station. |
| System Database | additional properties | See following section. |
To change the encryption state, right click .

| Property | Value | Description |
|---|---|---|
| System Database | read-only | Shows selected systemDb. |
| Orient Db Server Config File | module://orientSystemDb/rc/orientdb-server-config.xml |
Read-only field, shows the name of the backend server configuration file. |
| Database Encryption | Encrypted (default) or Unencrypted |
Read-only field, indicates current Encryption state. |
Five actions are available on System Database.
Use Start Database Action Menu to manually start the backend System Database process, when the System Database is not running. This action automatically pop up when the parent SystemDbService Starts. So no need to invoke it manually. It is useful when debugging in conjunction with the Stop Database action.
Manually stops the backend System Database process. This action automatically pop up when the parent SystemDbService Starts. So no need to invoke it manually. It is useful when debugging in conjunction with the Start Database action.
Manually deletes entries that are previously indexed into the System Database for particular NiagaraStations. Normally system indexing updates the System Database, but if a NiagaraStation is manually removed from the NiagaraNetwork or NiagaraStation is renamed then use this action to manually remove old System Database entries.
Deletes all entries from the System Database. It clears and restart the System Database. You need to wait for the next scheduled System Index operation or manually invoke it to repopulate the System Database entries after invoking this action.
In
Disabled to improve performance.