Compliance Job - General

The General panel lets you provide information that identifies a Compliance Job and provides some options for how the job should execute.

Field definitions

Name

Identifying name.

Description

Optional descriptive text.

Save in

Folder in which to store the object.

Set execution override

Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

Clear execution override

Remove an existing execution override.

Number of targets to process in parallel

Choose one of the following options:

  • Unlimited — Simultaneously runs the job on as many servers as possible. Application Server settings control the number of targets the job can access.
  • Limited — Specifies the maximum number of targets on which the job can run simultaneously. Limiting the number of targets is useful when a job might temporarily disrupt the functionality of a target server, and you want to limit that disruption to a small fraction of your managed servers.
    If you want the job processed serially at the target servers, set this value to 1. Note, however, that although this is the best approach for achieving serial processing, it does not always guarantee full serial processing at all targets; the first two or three targets might still run in parallel.

Continue despite compliance data collection errors

Whether the job should continue even though it encounters required parts that are missing.
If you check this option, the Compliance Job completes with warnings even though individual components may not satisfy some compliance rules because parts are missing.

Was this page helpful? Yes No Submitting... Thank you

Comments