This panel summarizes the settings for all cleanup jobs defined for the Business Flow Manager or Human Task Manager on a particular cluster or server. The settings can be changed, deleted, or you can define new ones.
To view this administrative console page, click either or , then on the Configuration tab, in the Business Integration section, expand Business Process Choreographer. Because the cleanup service settings and cleanup service jobs are defined separately for the Business Flow Manager and the Human Task Manager, click either Business Flow Manager or Human Task Manager, then in the Additional Properties section, click Cleanup Service Settings. If you select the Configuration tab, changes will only affect the server after it is restarted. If you select the Runtime tab, you do not need to restart the server to activate any changes, but you must select Save runtime changes to configuration as well if you want the changes to persist after the server is restarted.
Links marked (online) require access to the Internet. Each link launches a search for the topic in the online information center. When search results are listed, select the topic that corresponds best to your configuration.
Check for updates to this topic (online)
Depending on whether you selected Business Flow Manager or Human Task Manager, the settings in this section control the cleanup service for the Business Flow Manager or the Human Task Manager.
The cleanup service can be can be enabled or disabled. Select the check box to enable the service.
| Property | Value |
|---|---|
| Data type | Check box |
| Default | Disabled (clear) |
The schedule for running the cleanup jobs.
| Type | Value |
|---|---|
| Data type | String |
| Format | This field uses the WebSphere crontab format <Seconds> <Minute> <Hour> <Day_of_the_Month> <Month_of_the_Year> <Day_of_the_Week> according to com.ibm.websphere.scheduler.UserCalendar |
| Example | To run the once per hour, use the schedule 0 0 * * * ? |
| Default | 0 0 23 * * ? (every night at eleven o'clock) |
If the cleanup takes longer than the time specified here, the current transaction slice for the current cleanup job is completed, then the current cleanup job is stopped, and no more cleanup jobs are run before the next scheduled cleanup.
| Type | Value |
|---|---|
| Data type | Integer |
| Default | 120 |
| Units | Minutes |
The size of the transaction for the delete operation.
| Type | Value |
|---|---|
| Data type | Integer |
| Default | 10 |
| Units | Business process or human task instances per database transaction |
Each time that the cleanup service is triggered, all defined cleanup service jobs are run in sequence. Depending on whether you selected Business Flow Manager or Human Task Manager, all cleanup service jobs that are defined for either the Business Flow Manager or Human Task Manager are displayed in the table. You can add, delete, or edit cleanup service jobs.
Click this button to open the details panel to create a new cleanup job for the selected cluster or server.
Click this button to delete the cleanup jobs that are selected in the table.
This column contains one check box for each cleanup job listed in the table. You can select one or more before clicking Delete.
The integers in this column indicate the sequence in which the cleanup jobs will be run, starting with number zero.
This column shows the names of all cleanup jobs. To display the details panel for a cleanup job, so that you can change the settings, click the name of the cleanup job.
This column shows the templates, for which the cleanup job will delete eligible instances.
The wildcard (*) means that all templates will be cleaned. For cleanup jobs for the Human Task Manager, if defined, the target namespace is provided in brackets, for example, myTaskTemplate (http://bpc/samples/task/).
This column lists the template instance states which qualify it for deletion.
This column shows when instances become eligible to be deleted. The time is measured from when the instance reached the qualifying state.
| Property | Value |
|---|---|
| Data type | List of space-separated integers |
| Format | Minutes Hours Days Months Years |
| Example | 0 0 1 0 0 indicates that instances become eligible for deletion one day after they reach a qualifying state. |