Introduction

• The JS7 database will grow according to the number of workflows and jobs being executed. This includes an increase of data in the following areas:
  • Order History, Task History, Order Logs, Task Logs
    • The history includes one record for each execution of an order and a number of records corresponding to the tasks executed with a workflow.
    • In addition, any log output created from jobs is stored in a compressed format.
  • Deployment History
    • Any operation to deploy e.g. workflows is recorded.
  • Daily Plan History
    • For each day the JS7 - Daily Plan Service will create respective orders that are maintained in the database.
    • In addition order variables are recorded with the Daily Plan History.
  • Audit Log
    • Each operation to modify the status of an object is recorded, this includes
      • orders created and submitted by the Daily Plan Service and by the Daily Plan view,
      • ad hoc orders added by users or clients using the JS7 - REST Web Service API
      • deployments of workflows and related objects
      • operations that suggest intervention such as to cancel, to suspend and to resume orders.
    • The Audit Log is persisted with both the database and the respective log file, see JS7 - Log Files and Locations

Smart Cleanup Service

The JS7 - Cleanup Service is a background service that purges the database at configurable intervals.

• This service runs in background and is not subject to user intervention from the GUI except for adjusting its configuration.
• This service is designed to be executed while workflows, jobs and other services are running. As soon as it detects such database activity it will safely complete its current purge transaction and will