Configure the usage purge task
To configure the usage purge task, go to the task configuration page in the Services Framework user interface and select the New Task Configuration link.
The following table shows the information that is needed to configure the usage purge task.
| Field | Description | Example |
|---|---|---|
| Task | This field displays a list of all of the registered tasks. Select the name of the usage purge task that was entered during registration. | Usage Purge Task |
| Configuration | Descriptive name for the configuration. This field is required and can contain up to 60 characters. | Usage Purge Task |
| Description | A detailed description that explains what the configuration does. This field is optional. If entered, it must be 512 characters or less. | Purge all usage records older than 5 days. |
| Activate task | Identifies if the configuration is active. When it is active, the task is available to purge usage records. | Yes, No |
| Process end of day | Set this value to no because the task does not need to run at the end of the day. | No |
| Process cleanup | Set this value to no because the task does not need to process cleanup. | No |
| Keep days | Represents how long to keep the task usage records before they are purged from the
database. The purge process subtracts the keep days from the current date and time to determine which records
to purge. The minimum value for this field is 730 days. |
If the keep days is set to 735 and the current date and time is 18 May 2009 at noon, the purge process deletes all usage records older than 13 May 2007 at noon. |
| Commit rate | The maximum number of records to delete before a database commit is done. | If the commit rate was set to 500, the purge process does a database commit after every 500 usage records deleted. |