Skip to main content

System Maintenance Checklist

A collection of configuration and data housekeeping tasks that should be reviewed once during initial setup and regularly during ongoing operations to keep a managed ADITO system stable and performant.

Database Tables​

ASYS_AUDIT​

This table was originally designed for ADITO Offline Sync. It is not the content of the log tab.

Unless there is an explicit project-level use case, the table should be empty and remain empty.

ASYS_MAILREPOSIT​

This table stores a copy of the original emails fetched by the mail bridge. When active, ADITO can end up storing the same email up to three times: once in ASYS_MAILREPOSIT, once as an activity, and once in the binaries (or file browser) as an activity attachment.

Prefer using the mail inbox directly instead. Unless there is an explicit project-level use case, the table should be empty and remain empty.

ASYS_BINARIES​

All binaries should be stored in the file browser. The BINDATA column should be empty in every row and should stay that way.

ASYS_PROCESSHISTORY​

Depending on the number of processes and the frequency of their intervals, this table can accumulate hundreds of thousands of rows quickly. Set up a regular (automated) cleanup that removes entries older than a project-defined retention period.

AB_LOGHISTORY​

Every change made in the client is recorded here. Depending on the number of users, this table can grow rapidly. Set up a regular (automated) cleanup that removes entries older than a project-defined retention period.

ASYS_NOTIFICATIONS & ASYS_NOTIFICATIONSCONTENTS​

When users observe many records or filters, a large volume of notifications can be generated. Set up a regular (automated) cleanup that removes entries older than a project-defined retention period.

Preferences​

databaseAuditAlias​

This setting controls whether rows are written to the ASYS_AUDIT table. The value should be empty.

databaseAuditAlias

blobHandlingMethod​

This setting controls how the blobHandler process stores documents — either in the database or via the file browser.

Set the value to PROCESS.

warning

Changing this on an existing system only affects new or updated documents. Existing binaries must be migrated separately.

blobHandlingMethod

mailBridge​

Configure the mail bridge to avoid unnecessary data storage and excessive polling intervals:

  • Bridge mode: set to Process so that emails are processed directly without populating ASYS_MAILREPOSIT.
  • Interval: set to at least 1 minute to allow enough processing time and to reduce load on both the mail server and the ADITO server.

mailBridge

Indexsearch​

  • The index search should be enabled.
  • FullIndexerInterval should be set to 0.
  • The incremental indexer should run no more frequently than every 15 seconds.

Indexsearch

Configuration​

Logging​

For managed ADITO systems, no special logging settings are required. The file log should remain active to allow review of past log entries. All other logging options are unnecessary and cost server performance.

Debug-level logging and performance-log thresholds should only be activated temporarily for troubleshooting purposes.

Logging

Front-Pod vs. BG-Pod​

Mail Bridge​

Mail bridges should run exclusively on the BG-Pod, not on front web pods. The relevant aliases must also be configured in the BG system, and the corresponding configuration settings must be in place.

Processes​

Processes should be started on the BG-Pod unless there is a specific reason to do otherwise. This avoids unnecessary load on the front web pods.

Processes