[NextGenArch]

[NextGenArch] backendRestartDelay

Type: uint
Default: 20

Allows to configure the delay (in seconds) between the startup attempts of the database backend.

[NextGenArch] disableAuthConfigConnect

Type: bool
Default: 0
Range: 0|1

When the authorization config (_auth) is checked, much load is put on the EVENT manager. To decrease this load, the config entry "disableAuthConfigConnect" can be used. If the entry is set to 1, "connect to all authorizations" is disabled and permissions are only loaded on startup of the NGA and are not updated at runtime.

[NextGenArch] maxAlertHdlDetail

Type: int
Default: 10
Range: Alert range
Unit: Alert range

Specifies the highest alert range that is archived. By default the range is 10. This means that alerts including the _alert_hdl.10 are archived. An alert with the range 11 is not archived anymore. If several alerts must be archived, specify a higher value.

NOTE: If you specify a higher value, it has a big impact on the performance of the system. Therefore, the value must correspond to the project settings.

[NextGenArch] maxSecondsToWaitForInitialQueriesBeforeConnectingToEvent

Type: uint
Default: 60
Range: Seconds
Unit: Seconds

Specifies the time how long the error messages (that the EVENT manager was not started) are suppressed in NGA. The value must be as high as the time that EVENT manager requires in order to start.

In general changing this entry is only required for larger projects where the start of the EVENT Manager may take some time. Directly connecting to the EVENT Manager without this delay would cause the log to be filled with "cannot connect to event manager" messages.

NOTE: The EVENT Manager connection can still be configured as before by using the config entries connectDelay and connectRetries.

[NextGenArch] smoothBit

Type: string
Range: Userbit 1.. Userbit 32, _active, _exp_default, _aut_default, _out_prange, _out_range, _exp_inv, _aut_inv, _online_bad, _default_bad, _from_GI, _from_SI, _per_active, _stime_inv, _uncertain

This entry specifies which status bits should be considered for a smoothing by the NGA (low-level old/new comparison before archiving). If one of these user bits changes, the value is not smoothed out even if the original values would not have changed. This entry has to exist for each user bit that should be considered. Possible values for the user bits are:


smoothBit = "_active"
smoothBit = "_exp_default"
smoothBit = "_aut_default"
smoothBit = "_out_prange"
smoothBit = "_out_range"
smoothBit = "_exp_inv"
smoothBit = "_aut_inv"
smoothBit = "_online_bad"
smoothBit = "_default_bad"
smoothBit = "_from_GI"
smoothBit = "_from_SI"
smoothBit = "_per_active"
smoothBit = "_stime_inv"
smoothBit = "_uncertain"
smoothBit = "Userbit 1"
smoothBit = "Userbit 2"
smoothBit = "Userbit 3"
smoothBit = "Userbit 4"
smoothBit = "Userbit 5"
...
smoothBit = "Userbit 30"
smoothBit = "Userbit 31"
smoothBit = "Userbit 32"

[NextGenArch] timeoutForEventManReadConsistency

Type: int
Default: 30
Range: Seconds
Unit: Seconds

When a _dp_fct from the event manager requests a historical time range that is currently being written into the database, it has pending buffers that the Backend/Database must still write. In this case NextGenArch will wait at maximum the "timeoutForEventManReadConsistency" time for the pending writes to be completed. After the timeout has expired, the request is sent even if the values are not written. This can cause inconsistent results in the _dp_fct since the event manager expects that the _dp_fct will consider recent dpSets.

Value 0 disables the read consistency checks (not recommended).

Value -1 specifies an infinite timeout and guarantees read consistency.

Values smaller than -1 are ignored and the default of 30 is used instead.

This only applies to requests from the event manager via _dp_fct configs. All other historical requests or queries (CTRL, UI or custom managers) are not subjected to read consistency checking.

[NextGenArch] triggeredArchiving

Type: int
Default: 0

Allows to define the behavior for triggered archiving. A triggered archiving is performed, if the _archive config is set active. In this case all DPEs of this archive configuration are handled as if they received a hotlink with the current value.

Note: Can only be used for DPEs that have a _archive config.

Possible settings are:

0 - default; Triggered archiving is not performed.
1 - When the value is sent to the backends, the latest timestamp of the DPE is used.
2 - When the value is sent to the backends, the timestamp of the dpSet() operation is used.

[NextGenArch] useOriginalValue

Type: int
Default: 0
Range: 0|1

0: NGA connects to _online values as before. The behavior is unchanged. 1: NGA connects to _original values instead of _online values. This changes the meaning of the columns in the database as _original values are now archived instead of _online values.

The config entry can be used for large data point structures that contain many sub elements since NGA connects to all _online configs and the EVENT manager becomes slower.