Schedule automated maintenance tasks

To run server-side tests in ALM, the lab system must be up and functioning correctly. Scheduled automated maintenance tasks provide constant monitoring of the system's key components in order to detect system failures. You use the Lab Management > Maintenance Tasks module to check the status of the system.

To view and schedule maintenance tasks performed by the system:

  1. Log in to Lab Management from the ALM qcbin page.

  2. On the sidebar, select Lab Settings > Maintenance Tasks.

    The following fields are available in the maintenance task grid:

    Field Description
    ID ID of the maintenance task.
    Name Name of the maintenance task. Click the name link to view task details or change the run frequency.
    Recurrence (minutes) The frequency of the maintenance task.
    Description A description of the maintenance task.
    Last Execution Time The last time the maintenance task was executed.

  3. Click a maintenance task to view the details or change the run frequency.

    The following table describes the maintenance tasks:

    Maintenance Task

    Description
    Check Host Task

    Verifies the host installation, and updates the host status to either Operational or Non-Operational.

    Default frequency: Every 15 minutes
    Data Processor Task

    Sets and updates a data processing queue for any of the following actions: Analyzing a test run, recalculating the SLA, or adding test runs to a trend report.

    Default frequency: Every minute
    Handle Non Polling Functional Hosts

    Checks the Last Poll Time field of all registered Functional testing hosts. If a testing host has not been active for a long time, this task changes the status of the testing host to Idle or Non-Operational.

    Default frequency: Every 5 minutes
    OFW Status Update Task

    Updates the real status (Operational or Non-Operational) of a host that is located over a firewall.

    Default frequency: Every 15 minutes
    Orphan Run Task

    Identifies orphan test runs during and outside of the active timeslot.

    Default frequency: Every 15 minutes
    Resource Recovery Task

    Performs predefined validation tests on Controllers and load generators that are in the Non-Operational state. If the host passes the test, its status changes to Operational.

    • Controller validation tests. Tests the OTA connection, ability to run, and available disk space.

    • Load Generator validation tests. Tests the connection to the agent.

    The task parameters should be within the following guidelines:

    • MIN_APPLICATION_DIR_DISK_SPACE: Between 10 and 1000

    • CHECK_LG_TIMEOUT: Between 1 and 15

    • MAX_RETRIES: Between 1 and 1000

    Default frequency: Every 15 minutes

    Note: For load generators over a firewall, this is performed by the OFW Status Update task (see above).
    Result Cleaning Task

    Cleans test run results from Controllers or load generators in the following instances:

    • If the results have already been collated.

    • There are old performance tests whose results were not collated.

    • If the performance test was deleted.

    The RESULT_EXPIRY_DAYS task parameter should be between 1 and 1000.

    Default frequency: Every 360 minutes (6 hours)
    Synchronize Lab and SA times

    Finds the time difference between Lab Management and Site Administrator and enters it into the parameter SA_LAB_TIME_DIFF_MILLIS in the DATACONST table.

    Default frequency: Every 5 minutes
    Handle Stale Execution

    Handles Stale Execution items that have not been updated by the client for a while.

    Default frequency: Every 5 minutes

    You can use the STALE_EI_TIMEOUT_IN_MINUTES parameter to specify the time length (in minutes) that an execution task can stay in a status before it is considered as stale. For details, see Set configuration parameters.
    Orphan PAL Reports Task

    Deletes report items that are not a part of any report.

    Default frequency: Every 1440 minutes (24 hours)
    Publish Runs for Trending

    Automatically adds runs to trend reports.

    Default frequency: Every hour
    Check Timeslot Task

    Checks active timeslots and handles idle instances.

    Default frequency: Every 5 minutes.

Back to top