Scheduling Accumulated Data Cleanup for Domains

Periodically clean up accumulated data maintenance items in cache that are no longer needed, by creating a data purge schedule. Set the schedule to perform the clean up processes when system usage is low.

1. In the SAP Control Center left navigation pane, expand the Domains tab and select a domain.
2. In the right pane, select the Scheduled Tasks tab.
3. Under Task, select one of the options you want to schedule, and then select Properties to set up its automatic schedule:

   Option	Description
   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. Note The last synchronization time of a client is the last time the client successfully applied the download. Because the SAP Mobile Server does not require download acknowledgement, the SAP Mobile Server only knows that the previous download was applied successfully when the client synchronizes for the second time (uploading the previous synchronization time). The synchronization time on record in the system is normally the time the 'second last' synchronization happened. 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.

4. Click Properties, then in the Task Properties dialog, select the Schedule tab.
5. Configure the required schedule:
   • Schedule repeat – select how often the schedule should run. Options are daily, hourly, custom, and never.
     • If you select daily or hourly, specify:
       • Start date – select the date and time the automated upload should begin. Use the calendar picker and 24-hour time selector.
       • End date – select the date and time the automated upload should end.
       • Days of the week – select each day the automated upload schedule should run.
     • Select custom, to specify the interval granularity in seconds, minutes, or hours, as well as other date and time parameters.
6. In the Task Properties dialog, select the Options tab, and set the number of inactive days for which to purge.
   For Subscription Cleanup, Error History Cleanup, and Client Log Cleanup, set the number of inactive days for which to purge. For Synchronization Cache Cleanup, set the purge interval for EIS managed caches. For more information on EIS-managed caches, see EIS Defined Cache Partitions in Mobile Data Models: Using Mobile Business Objects and Creating Cache Groups in SAP Mobile WorkSpace - Mobile Business Object Development.
7. Click OK to save the schedule properties and purge options.
8. Select Enable. Schedules run until you disable them, or until they expire.