Subscription Cleanup |
Removes subscriptions that are inactive for the
number
of days specified in the schedule task configuration. A
subscription is considered active based on: - Replication – last synchronization
request timestamp.
- Messaging – last synchronization message
timestamp.
A user who infrequently accesses the system, for example, 3-4
times a year, falls outside the specified time frame and is
removed from SAP Mobile Platform. He or she must
then reinstall the application and initiate a sync to reactivate
the subscription.
|
Error History Cleanup |
Removes historical data on MBO data refresh and operation replay
failures, which result from system or application failures.
System failures may include network problems, credential issues,
and back-end system failure. Application failures may include
invalid values, and nonunique data.
Only error messages are removed.
|
Client Log Cleanup |
Removes logically deleted client
log records that have already been synchronized to the device, or
are no longer associated with active users. |
Synchronization Cache
Cleanup |
This cleanup task removes:- Logically deleted rows in the cache that are
older than the oldest synchronization time on record in the
system. Synchronization activity for all clients establish
the oldest synchronization time.
- Unused or stale partitions.
In
addition, the optional exp header property in
DCN messages indicates an expiration date, after which the data
is purged based on the defined Synchronization Cache Cleanup
schedule.
|