Maintaining The Uca Server; Scheduled Data Maintenance - Motorola CA50 Developer & User Manual

14 - 2 CA50/UCA Client & Server Developer & User Guide

Maintaining the UCA Server

Maintaining an installed UCA server requires:
•

Scheduled data maintenance

•
Keeping system data and configuration up to date.
Scheduled Data Maintenance
There are some data maintenance tasks that the UCA server periodically performs. It exports and purges debug
trace data and metrics data. It also purges recent user records, device records and phone extension status
records.
The UCA Maintenance Service manages this maintenance. It can run every day at the configured hour (system
setting: System.Maintenance.DB.Hour). It can be configured to skip days according to the system setting:
System.Maintenance.DB.DaysBetween.
Each area of maintenance has its own set of system settings:
•
System.Maintenance.DB.DebugTrace
•
System.Maintenance.DB.Metrics
•
System.Maintenance.DB.Devices
•
System.Maintenance.DB.LocalUser
•
System.Maintenance.DB.PhoneExt
•
System.Maintenance.DB.CallParkExt
Only the DebugTrace and Metrics generate export files. The files are written into the folder specified by
System.Maintenance.DB.Export.Path. Both of these maintenance items has a FileAging setting. This setting
controls how many automatic export files for this item are left in the export folder after it exports the current set of
records.
All of these maintenance items have a DaysBetween setting. This controls how often the maintenance item runs.
This is a threshold that is checked when the overall maintenance runs according to
System.Maintenance.DB.DaysBetween. If the overall maintenance schedule is longer than one day, then any item
set to more frequently than the overall schedule only runs according to the overall schedule.
All of these maintenance items also have a RecordAging setting. This setting controls how long a record is allowed
to remain in the database before it is purged and optionally exported.
NOTE Devices and Local Users are recommended to be a relatively long interval, while Debug Trace is
recommended to be set at daily.