|
The Direct Persistence and Data Table have schedulers specific to their services. Even if schedulers for both implementations are enabled and configured, only one of them will execute the archive service. More specifically, only the service corresponding to the active implementation of the AuditSubsystem will run. By default, if the other scheduler is active, it will try to run the archive service, but since its implementation is disabled, it only logs a WARN message, that it tried to execute the archive service but failed since the other implementation is enabled.
|
Implementation
|
Audit Service
|
Scheduler Thing
|
---|---|---|
Direct Persistence
|
ArchiveAuditHistoryDirectPersistence
|
AuditArchiveSchedulerDirectPersistence
|
Data Table
|
ArchiveAuditHistory
|
AuditArchiveScheduler
|
Both
|
PurgeAuditData
|
AuditPurgeScheduler
|
Both
|
AuditArchiveCleaup
|
AuditArchiveCleanupScheduler
AuditArchiveCleanupNotificationScheduler
|
|
Never disable the purge scheduler. Doing so prevents the system from periodically copying the online audit data to the offline repository and then deleting it. Allowing the online data to accumulate to a very high amount without periodic purge operations may eventually bring the platform down.
|
The schedulers have a property that shows the last run time of a scheduled job, called LastArchivedTime for the Data Table implementation archive service or LastArchivedTimeDirectPersistence for the Direct Persistence implementation archive service. After every successful run of a scheduled job, the system updates this property. Note that although it is possible, this property should never be edited manually. |