(Glue-2111) Cleanup Watchdog

Owned by SNP
Nov 22, 2021
3 min read

Transaction: /DVD/GL_C_WATCHDOG

This transaction can be accessed also via the GLUE Cockpit.

The Cleanup Watchdog is a periodically executed background job that looks for old GLUE data that is no longer needed - the conditions are specified by the user. The settings can be changed only when:

  1. The user has been switched into the Edit mode

  2. No other user is currently editing the settings

  3. The Cleanup Watchdog is not running

Only one instance (one background job) of the Cleanup Watchdog can be running at the time. The Cleanup Watchdog can be started using the Start Watchdog button and stopped using the Stop Watchdog button. Be aware that these buttons can be used only in the Edit mode. Clicking on the Refresh button will load the latest execution data.

Common settings

These settings are common for all types of the Cleanup Watchdog. They specify the main attributes of the Cleanup Watchdog job.

  • Background job name - the name of the background job which will be Cleanup Watchdog running under

  • Execution period - specifies the periodicity of a background job - the job will be executed every XY Years/Months/Days, etc.

Currently, there is only one type of the Cleanup Watchdog available - GLUE requests. The other types (Mass execution, FIFO queue, TEMP files, etc.) are temporarily disabled.

GLUE Requests

GLUE Requests Cleanup Watchdog cleans up GLUE Extractor 2.0 requests based on the settings that are set. The settings are available for editing after clicking on the GLUE requests tab. The GLUE requests settings are consisting of:

  • Cleanup Watchdog enabled - enables or disables the execution of the GLUE requests type of Watchdog

    • Must be checked, otherwise, this type of Cleanup Watchdog won’t be executed

  • Storage data cleanup - enables or disables the deletion of the storage data bound to a certain request number

  • Retention period - enabled by default - specifies what requests are considered as old/to be deleted

    • Example: Older than 1 year, 6 months, 1 week

  • Status - specifies which requests statuses are marked for cleanup

    • Example: all requests that finished with an error, warning, failure

  • Username - specifies which user’s requests are marked for cleanup

    • The default value is always the logon username

  • Extraction process - specifies which requests belonging to a particular extraction process shall be cleaned

  • Rows read - specifies which requests shall be cleaned based on rows read

  • Rows written - specifies which requests shall be cleaned based on rows written

If multiple settings are enabled, these settings are accumulated - if the username ‘SAPUSER' is checked together with status ‘F', deleted will be all requests of user 'SAPUSER’ AND the status 'F’.

GLUE QUEUE

GLUE QUEUE Cleanup Watchdog cleans up GLUE QUEUE data based on the settings that are set. The settings are available for editing after clicking on the FIFO queue tab. The GLUE QUEUE settings are consisting of:

  • Cleanup Watchdog enabled - enables or disables the execution of the GLUE QUEUE type of Watchdog

    • Must be checked, otherwise, this type of Cleanup Watchdog won’t be executed

  • Retention period - enabled by default - specifies what data are considered as old/to be deleted

    • Example: Older than 1 year, 6 months, 1 week

  • Username - specifies which user’s queues are marked for cleanup

    • The default value is always the logon username

  • Queue name - specifies what data are deleted based on queue name. This option also supports patterns for example ZDVD*.