Configuring background job execution strategy

The following table describes how to replicate the background job execution strategies that existed prior to Application Security version 25.2.0.

Legacy job execution strategy Description Configuration instructions

Conservative

Balances job concurrency, throughput, and job stability.

No changes required.

Aggressive

Enables high concurrency. With this strategy, the job scheduler does not enforce any limitations on how jobs are executed. All jobs are equal and executed on all available workers.

OpenText does not recommend using this job execution strategy.

Set job.exclusiveJobOverheadPercentage to 0.
Set job.numberOfConcurrentReports to the same value as the jobs.threadCount value.

OpenText recommends using a smaller value than the jobs.threadCount value or the default value of 2 to increase scan processing throughput and reduce peak memory that report generation can consume.
Set job.numberOfConcurrentExclusiveJobs to the same value as the jobs.threadCount value.

OpenText recommends that you use the default value of 1 to increase scan processing throughput and avoid lock contention in the database.

Exclusive jobs

Enables jobs to run in sequence and one at a time.

OpenText does not recommend using this job execution strategy.

Set jobs.threadCount to 1.
Set job.numberOfDedicatedDataExports to 0.