MES Curator Host service configuration settings

CurationTransaction
TimeLimit

The amount of time alloted for data curation from the MES production database before logging a message.

The default setting is 30 seconds.

Note: This setting should not be confused with the transaction time out.

This setting is used at runtime to evaluate the duration of the call, and if it exceeds the configured duration, then it records the message in the logger. Diagnostically, logged messages can be used to determine which calls are taking longer than the configured amount of time.

DeadlockTimeOut
RetryCount

The number of times the system will retry after it detects a failed deadlock or timeout transaction.

The default setting is 3 counts.

For example, using the default setting, the system will try to successfully complete a transaction 4 times.

DeadlockTimeoutRetry
MaxWaitTime

The amount of time to wait between each retry to allow the system to free up used resources in the previous transactions.

The default setting is 1500 milliseconds.

ForcedGarbage
CollectionFrequency

The interval at which to force .NET framework garbage collection. The interval is specified in minutes with a default value of 480 minutes (8 hours).

While the value is configurable, AVEVA recommends that you use caution in decreasing the default setting because application performance could be impacted.

MaxRetryOnLicenseValidation

The number of times that the curator service will attempt to retrieve a cloud license from the MES middleware.

There is a 25 seconds gap between each attempt.

The default setting is 25 retries.

The maximum number of retries allowed is 50 retries.

Note: When using MES Cloud integration with MES 2023 R2, the 'CloudLicensed' feature must be enabled for the cloud integration to work. On startup, the MES Staging Curator Service component attempts to read the license information from the MES middleware. If a valid license is obtained, the curator service continues to run. When a valid license is not obtained, the curator service logs an error in the System Management Console (SMC) log viewer and exits.

MaxRowsToReadPerCallOnDataCuration

The number of rows to be curated at a time.

The default setting is 5000 rows.

If the MES Curator detects more than 5000 changes at a time when it is polling for changes, then the curation is divided into groups of 5000 records.

For example, if the MES Curator detects 23000 changes when it polled for data change, then the curation will curate 4 times with 5000 records each, and the 5th set will have 3000 changed records.

This setting applies to both upserts and deletes when curating data.

TimeDelayForCuration

The amount of time (in minutes) to delay the data curation.

The default value is 4 minutes.

The MES Curator service adds an additional 1 minute to this setting for a total default delay of 5 minutes.

If TimeDelayForCuration is less than or equal to zero (<=0), then it defaults to 4 minutes at runtime. If TimeDelayForCuration is greater than 60 minutes (3600 seconds), then this setting defaults to 60 minutes at runtime.

Note: For data curation work, the runtime automatically adds 1 minute on top of this time delay to scale back the requests to read the committed transactions.

When more than one MES middleware is used against an MES production database, then the highest transaction timeout from those middleware's is used. The transaction timeout may have been configured in seconds in the MES production database, which is converted to minutes (rounded to the next highest integer) when specifying the value for this time delay.

TransactionTimeout

The maximum amount of time a transaction can take to complete. The transaction includes the Web API requests, data curation from the production MES database, storage of the curated information in the staging schema, cleaning up the curated logs, etc.

The default setting is 60 seconds.

If TransactionTimeout is less than or equal to zero (<= 0), then it defaults to 60 seconds (1 minute) at runtime. If TransactionTimeout is greater than 3600 seconds (60 minutes), then it defaults to 3600 seconds at runtime.

Note: For the Web API request calls, the runtime automatically adds 1 minute on top of this transaction timeout to scale back the requests to read the committed transactions.

TypesToUpdateFrequently

A list of MES data types that should bypass the default transactional delay and be curated immediately upon receipt. This setting ensures that time-sensitive types such as MESJobOrder, MESMaterialConsumedActual, MESMaterialProducedActual, and MESMaterialInventory are updated in near real-time using the Events to CONNECT end time directly, while the start time is still scaled back by the Curator service.

If TypesToUpdateFrequently is omitted or contains invalid entries such as junk values or duplicates, the system ignores them at runtime and applies the standard delay behavior. Type IDs are case-insensitive and must match entries in the staging_type_config table. This setting complements curate_frequency but specifically targets delay elimination rather than frequency control.

WebApiTransaction
TimeLimit

The amount of time alloted for a Web API call to complete before logging a message.

The default setting is 30 seconds.

When the Web API call takes longer than the configured amount of time, then a message is recorded in the logger about the type (for example, util_history, item_prod, etc.) that is taking longer to return data.