Configuring job scheduler attributes

You can configure scheduling attributes for processing Application Security background jobs.

To configure job scheduler settings:

  1. On the header, select Administration.

  2. On the navigation pane, expand Configuration, and then select Scheduler.

  3. On the Scheduler page, configure the settings as described in the following table.

    Field

    Description

    Number of days after which executed jobs are removed

    Type the number of days after which finished jobs are removed. The default value is 1 (day).

    Canceled jobs are removed daily.

    Pause job execution

    This check box (not selectable from the Scheduler page) shows whether job execution has been paused (from the Maintenance page) in preparation for server shutdown / system maintenance.

    To proceed to the Maintenance page to select or clear this check box, click the here link. A change to this setting takes effect immediately after you save the change from the Maintenance page. No server restart is required.

    After you pause job execution, jobs (artifact processing, report generation, data export requests, and so on) that are currently running continue to completion. Any new jobs submitted are queued for processing after the Pause job execution check box is clear and regular processing resumes.

    OpenText strongly recommends that you pause job execution immediately before server shutdown, and keep it paused for as short a period of time as possible. This prevents a high volume of jobs from queuing up for processing later.

    Job execution does not automatically resume after the server comes back up after maintenance. To resume job execution, you must return to the Maintenance page and clear the Pause job execution check box.

    Token management
    Token expiration alerts

    Type the number of days before token expiration that users are notified of the upcoming expiration. Valid values range from 3 to 30 days, inclusive.

    The default value is 7 (days).

    The start of the day is 12 AM in the Application Security server locale.

    Snapshot refresh Use the fields in this area to schedule the snapshot job.

    A snapshot is application version information captured at a given moment in time. This information includes variables and performance indicator values, which calculates application versions trends at the scheduled times.

     The values you enter in the Days of the week, Hours, and Minutes boxes are concatenated to create the cron expression the scheduler uses.

    Days of the week

    Use cron syntax to specify the days of the week on which the historical snapshot job is to be run. You can use a three-letter abbreviation for the day of the week (for example, enter THU for Thursday) or as a single digit, by entering a 1 for Sunday, a 2 for Monday, and so on. To run the scheduler on multiple days, separate the entries with a comma. For example, enter SUN,WED,FRI or 1,4,6.

    Use uppercase letters for three-letter abbreviations. Spaces between the entries are optional.

    To specify consecutive days, separate the entries with a dash. For example, enter MON-FRI to run the scheduler on week days only.

    Enter an asterisk (*) run the scheduler every day (the default).

    Hours

    Type the hour, using 24-hour time notation, at which the recurring scheduler job is to start running. For example, enter 1 to start the job at 1 AM.

    Enter an asterisk (*) to run the scheduler every hour.

    The default value is 0 (midnight).

    Minutes

    Type the minute at which the recurring scheduler job is to start running. For example, enter 24 to start the job at 24 minutes past the hour that you entered in the Hours box.

    The default value is 0, which indicates that the job starts running in the first minute.

    Index maintenance Use the fields in this area to schedule your Application Security full text search index maintenance. OpenText recommends that you run this job daily.

    The values you enter in the Days of the week, Hours, and Minutes fields are concatenated to create the cron expression the scheduler uses.

    Days of the week

    Use cron syntax to specify the days of the week on which the index maintenance job is to be run. You can enter the value as a three-letter abbreviation for the day of the week (for example, use THU for Thursday) or as a single digit, by entering a 1 for Sunday, a 2 for Monday, and so on.

    To run the scheduler on multiple days, separate the entries with a comma. For example, enter SUN,WED,FRI or 1,4,6.

    Use uppercase letters for three-letter abbreviations. Spaces between the entries are optional.

    To specify consecutive days, separate the entries with a dash. For example, enter MON-FRI to run the scheduler on week days only.

    Enter an asterisk (*) to run the scheduler every day (the default).

    Hours

    Type the hour, using 24-hour time notation, at which the recurring index maintenance job is to start running. For example, enter 1 to start the job at 1 AM.

    Enter an asterisk (*) to run the scheduler every hour.

    The default value is 0 (midnight).

    Minutes

    Type the minute at which the recurring index maintenance job is to start running. For example, enter 24 to start the job at 24 minutes past the hour that you entered in the Hours box.

    The default value is 0, which indicates the job starts running in the first minute.

    Events maintenance
    Days to preserve

    Type the number of days after which Application Security removes past events. To specify no event removal, enter 0 (zero).

    Application Security uses the new value during the next run of the dedicated cleaning job. A new job is created daily at 11:30 PM and if it is not blocked, it starts its work immediately.

    The default value is 0, which indicates that no cleanup occurs.

    Reports maintenance
    Days to preserve

    Type the number of days Application Security is to retain generated reports. The default value is 0, which indicates that no cleanup occurs.

    To ensure that the cleanup job is not too time- or resource-intensive, each nightly run clears a maximum of 2000 old reports (and associated entities). Application Security then gradually cleans up the remaining reports over the following days.

    Data export maintenance
    Days to preserve

    Type the number of days Application Security is to retain exported audit reports.

    The default value is 2.

    This job is run every day at 11:45 PM (23:45)

  4. Click SAVE.

  5. To apply your settings, restart the server.

See Also

Setting job execution priority

Configuring background job execution strategy

Canceling scheduled jobs

Recurring cleanup jobs