Configuring the attribute store cleanup task

You can control the way IBM MobileFirst™ Platform Server cleans up stale data in the attribute store.

The properties described in this page became available starting from IBM MobileFirst Platform Foundation V7.1.0.

When the attribute store is configured to use the MobileFirst database, a cleanup task is run periodically to delete stale entries. Stale entries are attributes that have expired and have not been accessed for a period (the default is 30 days). The task is also applied when the attribute store is over eXtremeScale and the write-behind database is the MobileFirst database.

Attributes always have an expiration date (this is the expiration date of the realm with which the attributes are associated). An expired attribute is normally deleted the next time it is accessed. However, if the client application is no longer in use (for example, because it has been uninstalled), expired attributes that are associated with the client application are deleted by the cleanup task. Use the following properties to configure the cleanup:

Table 1. MobileFirst Server attribute store cleanup properties
Property name	Description
mfp.attrStore.db.cleanupFrequency.minutes	The attribute store database cleanup task interval (in minutes). The default is 60 minutes.
mfp.attrStore.db.stalePeriod.days	The interval (in days) after which an expired attribute is considered stale, and may be deleted by the attribute store database cleanup task. The default is 30 days.

An example of stale data cleanup: if the mfp.attrStore.db.cleanupFrequency.minutes property has been set to 10 and the mfp.attrStore.db.stalePeriod.days property to 30, then every 10 minutes, the cleanup task runs and deletes data that expired more than 30 days ago.

For more information about session dependency, see Session-independent mode.