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

The referenced document [xwiki:Automation-DevSecOps.Server-Automation.TrueSight-Server-Automation._inclusionsLibrary._Job_wizard.WebHome] was not found.

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 , 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  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*