Purpose

• The Cleanup Service is used to purge historic data that are no longer required. This includes data from the JS7 - History, the JS7 - Daily Plan history and the JS7 - Deployment history.
  • The execution history and logs of orders and tasks is purged.
  • The history of submissions to the Daily Plan is purged.
  • The deployment history is purged.
• A purge of historic data is performed in order not to fill up the JS7 - Database and to guarantee overall performance at an ongoing basis.
• For organizations that are subject to compliance requirements different retention policies might apply e.g. when it comes to the period for which task logs should be stored. In this situation consider the below mentioned default values for operation of the Cleanup Service and adjust them to your needs. This includes the option not to use the Cleanup Service and to manually purge the JS7 database.

Cleanup Order and Task History

When an order is launched for a workflow then this will create an order log and a task log. The order log includes any output of jobs and instructions in a workflow, the task log is available for each job individually. 

Therefore the number of records in the order and task history depends on the number of workflows and jobs executed in a given period. The size of historic records depends on the size of output that is logged by your jobs.

Cleanup Daily Plan History

The Da

Cleanup Deployment History

.

Configuration

Location

• The "Settings" menu is available from the JOC Cockpit GUI.

Configuration Items

Logging

• The Cleanup Service logs general messages, warnings and errors to the joc.log file.
• More detailed information in addition is logged to the service-cleanup.log file.
• For details see JS7 - Log Files and Locations