Set the timeframe for running background jobs

This topic explains how to set the daily timeframe when the system can run background jobs.

Background jobs recalculate the status of each request submitted before you upgraded to Deployment Automation 6.3.3 or later. They store the status in the database for easy retrieval, improving Deployment Automation performance in opening and processing timelines and deployment history.

Because background jobs may slow the server while they are running, we recommend that you limit them to a low or no activity time. To restrict background jobs to run during a specified timeframe, change the materializedViewJobsConfig settings in the server's da_config.xml file.

By default, the timeframe is set in a 24-hour format to a period between 19:00 and 07:00 according to your system's timezone.

Tip: To find out how many process requests need recalculating, navigate to Deployment > Timeline in the Deployment Automation web interface, and select the calendar view for a specific month or year. The number of such requests is displayed with the Unknown status icon. For details, see View deployment timelines.

To set the timeframe for running background jobs:

  1. Navigate to the Common Tomcat da\WEB-INF\classes directory, for example:

    C:\Program Files\Micro Focus\common\tomcat\8.5\webapps\da\WEB-INF\classes

  2. Open the da_config.xml file. This file contains your current timeframe settings.
  3. Copy the <materializedViewJobsConfig> settings from the da_config.xml file:




  4. Navigate to the DA user profile directory where the DA server configuration is stored, for example:


  5. Open the da_config.xml file in the DA user profile and paste the copied <materializedViewJobsConfig> settings there.

    Note: Every DA server upgrade restores the web application's da_config.xml settings to default. You need to add and configure these settings in the DA user profile directory to make them permanent.

  6. Edit the <materializedViewJobsConfig> settings in the da_config.xml file. Change the <allowedTimeframeStart> and <allowedTimeframeEnd> values to a new start and end time in a 24-hour format.

    Use this example of default timeframe settings, where the period is set to start at 7 pm and end at 7 am:

  7. Save your changes.
  8. Restart Common Tomcat.

To review the background jobs status, enter the following URL in your web browser:


Back to top

See also: