ACL Push Job - General

Use the General panel to provide information that identifies an ACL Push Job.

Field definitions

Name

The name of a job.

Description

Optional descriptive text.

Save in

Folder in which to store the object.

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.

Exclude Targets

NEW IN 20.02.01

Specify whether you want an ACL push job to exclude the targets where the File Server or Repeaters are installed.

  • If the File Server or Repeaters are registered with TrueSight Server Automation, use the same registered name while adding it to the ACL Push Job targets. Otherwise, ACL Push jobs cannot exclude the targets.

    Use the following blasadmin command to view the current File Server host setting:

    blasadmin show fileserver name
    For example, if the File Server is registered as fileserver1 and added to an ACL push job as fileserver1.bmc.com or <ip address>, the ACL push job will not exclude the target where the File Server is installed even when you select the check box for exclusion.

  • By default, both the check boxes are selected for a new ACL Push job.
  • After you upgrade to TrueSight Server Automation 20.02.01, the check boxes are not selected, which indicates that the targets are not excluded.

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.

Where to go from here

ACL-Push-Job-Targets

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*