Parameters
The parameters tab contains miscellaneous central parameters in the top application.
Name
This is the name of the top application. The name will be visible in the configuration area, and will also be registered in the database.
ReportEventLevel
This parameter can be used to filter what events that are written to the application log by the tracker. All events with equal or higher severity than the one chosen will be reported.
Sequential top application
If this parameter is true, the contained components of the top applications will be operated sequentially, and the order of the component is significant. When false, the order is insignificant, and delays may occur between chained components.
Intermediate state persistence
The Intermediate state persistence parameter decides when the tracker material data will be persisted to the database. The alternatives are:
- Disabled: Tracking material will only be persisted when the state changes, i.e. on material creation, material making and material exit.
- Continuously: Tracking material will be persisted whenever the material is changed, i.e. on amount changes and so on.
DB object caching
This option decides what types of database configuration objects to cache. Cached objects will be read from the database first time used, and fetched from the caches for later use. Examples of cached objects are MaterialQualities.
Log material quality history
If this parameter is true, material quality changes will be logged into the MaterialQualityLog table. For large databases there may be advantageous to leave this parameter off in order to save database space and increase performance.
Force port data exchange
If this parameter is true, data will be exchanged between connected ports even if the values have not changed. When false, data will be exchanged only if the source port has newer information than the destination port.This property is included to obtain backward compatibility, and may be removed in later versions of the tracker.
Offline transaction interval
The offline transaction interval (milliseconds) decides how often asynchronous transactions will be performed. This value cannot be less than 1000.
Offline transaction maximum time lapse
The offline transaction maximum time lapse (milliseconds) is the maximum amount of time used when writing a batch of asynchronous transactions since the tracker started.
Last offline transaction time lapse
The last offline transaction time lapse (milliseconds) is the amount of time used when writing the last batch of asynchronous transactions.
Persist database on shutdown
When this parameter is set to true, material amounts, material data capture, tracking material quality and run states are persisted to the database on shutdown.
Persist quality
This parameter controls the what quality (TraMaQualityCode) that shall be persisted when the tracker is shut down controlled.
Transaction lock timeout
The transaction lock timeout in milliseconds decides how long a message based (web based) transaction is allowed to lock the tracker. After this period the tracker is automatically unlocked and signal based transactions are allowed to run.
Max number of exclusive transactions
This parameter decides the maximum number of exclusive transactions allowed in a sequence. If this number is exceeded, the transaction lock will be unlocked in order to allow signal based transactions to take place. When the signal based transactions are finished, the transaction lock is locked again.
Max number of exclusive moves
This parameter decides the maximum number of material transfers allowed in a single transaction. If this number is exceeded, the transaction lock will be unlocked in order to allow signal based transactions to take place. When the signal based transactions are finished, the transaction lock is locked again.
Tracking event report level
This parameter decides the degree of reporting from the tracker. It is recommended that the level is set to ‘High’ in configuration or debugging periods.
Material outdate interval
This parameter (seconds) decides how often the tracker shall check the tracker process units for outdated material. If the property is set to 0.0, no material outdating will be performed.
Engine state report interval
The engine state report interval (seconds) decides how often to write information about internal tracker engine state to the event log. If the value is set to 0.0, reporting is disabled.