With Task Engine instances running on My webMethods Server, you can archive task instance details for auditing purposes. Task Engine uses the production database to store operational task data, and a separate data source for archiving the data for long periods of time. You can use any of the supported database types as a data source for archiving tasks. Before you can archive tasks to the required database, you must create a TaskArchival database component using the Database Component Configurator.

By default, Task Engine stores all data for a particular task instance in the archive, including the task business data fields and values.

When determining the conditions for archiving tasks, Task Engine uses the same approach as with global task rules. A task instance is archived when it reaches a state that meets a predefined condition, or set of conditions. You configure conditions as task rules, using a simple graphic interface on the Task Archival page. You can schedule the rule, so it executes automatically, or manually trigger the archiving of the task instances that meet the condition.

Task archiving is not enabled with an out-of-the-box Task Engine installation. You must enable task archiving before you can modify the configuration of the task archiving data source, or store task data.

When saving task data to an archive data source, Task Engine also stores the cluster ID. Each My webMethods Server/Task Engine cluster requires a separate data source for task archiving.

By default, the task archiving configuration in Task Engine includes a scheduled rule that, when enabled, triggers every hour to archive the eligible task instances. You can modify the rule to a schedule that suits your business needs.

Archiving a large number of task instances might require a considerable amount of time. Software AG recommends that you schedule task archiving carefully in order to avoid periods of time when the system is under heavy load.