Offer flexible options how to run the Cleanup Service

Current Situation

• JOC Cockpit's Cleanup Service works in a discreet way: it deletes data in batches (default: 1000 records) and checks if the History Service adds entries to the job history in parallel. Should this be true then the Cleanup Service terminates having processed the current batch and will restart later on.
• The reason being that some DBMS products are particularly sensitive to concurrent transactions: MySQL (InnoDB) does not offer row level locking for indices and will more frequently raise deadlocks. PostgreSQL and Oracle are less susceptible to concurrent transactions.
• For users of JS7 who operate high job load on 24/7 basis there might not be a single 10s timeslot throughout the week in which no jobs are started and in which cleanup can be performed safely. For such situations a number of additional options are made available to runthe Cleanup Service.

Desired Behaviour

• The Cleanup Service is added the following functionality:
  • to force start of the Cleanup Service at the given point in time.
    • If the option is not used then the behavior as specified in section "Current Situation" is applied.
    • If the option is used then no check is performed for concurrent transactions of the History Service.
      • Users can pause the History Service when the Cleanup Service is running.
        • Pausing the History Service includes to set a timeout that is in proportion to the batch size. Experience tells that a batch of 1000 records will be deleted in <2s.  The Cleanup Service will tell the History Service to consider the timeout in case that the Cleanup Service will not complete the current transaction and otherwise will release the History Service's timeout before expiration.
        • Users specify the duration of the pause and the delay after completion of the pause by which the Cleanup Service will restart.
• The Cleanup Service is added the operation "Start now"
  • In the Dashboard view the action menu for JOC Cockpit is added the following menu items:
    • Run Service
      • Cleanup Service
      • Daily Plan Service
  • The Cleanup Service will start immediately and will consider existing settings to pause or not to pause the History Service.
    • Note: A running Cleanup "Now" will stop if the cleanup settings are changed.
• The Cleanup Service should gracefully stop/abort the active statements when this service is restarted/stopped to avoid database locks.