<c:cleanupPolicy xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-2a"> <c:auditRecords> <c:maxAge>P3M</c:maxAge> </c:auditRecords> <c:closedTasks> <c:maxAge>P1M</c:maxAge> </c:closedTasks> </c:cleanupPolicy>
Removing obsolete information
During midPoint operation, some data items gradually gather in the repository. Typical examples are tasks and audit records.
MidPoint provides a feature that automatically cleans-up the repository with respect to these items. A system task named Cleanup runs (by default) every 24 hours and removes tasks and audit records older than predefined time value. This is the default configuration from the System Configuration object:
This configuration causes the Cleanup task to remove all audit records older than three months (see the ISO 8601 specification) and all closed tasks that are more than one month after their completion.
Note: More precisely, when removing the tasks, only root tasks are considered. When a root task is removed, all of its subtasks (that should be completed before the root) are removed as well.
Element type for
cleanupPolicy is documented in our schemadoc.
There are more
CleanupPolicyType elements available in
cleanupPolicy, not configured by default in the System Configuration object:
auditRecordsto clean up audit records,
closedTasksto clean up closed tasks,
closedCasesto clean up closed cases,
closedCertificationCampaignsto clean up closed certification campaigns,
outputReportsto clean up output reports,
deadNodesto clean up dead nodes.
The things mentioned above are cleaned up regularly by the Cleanup task.
There are other clean-up settings, but these are consulted only when the relevant structures are worked with:
objectResultsclean-up policy for object execution results - used as a default when the following settings are not specified,
simpleOperationExecutionsis used to clean up simple execution results,
complexOperationExecutionsis used to clean up complex execution results.