Important

   

This space contains documentation for TrueSight Server Automation 8.9.03 and the later service packs for 8.9. For earlier releases, see BMC Server Automation 8.9.

Reviewing the number of servers a job will impact

TrueSight Server Automation allows you to set and review the number of servers targeted by a job (target server). By default, this option is not enabled in TrueSight Server Automation. Reviewing the number of target servers before creating, modifying, or executing a job prevents you from running a job against a certain number of servers at once. For information about how to enable this option, see Enable messages to review the number of target servers in a job.

The message prompting you to review the number of targets is displayed for most types of jobs in TrueSight Server Automation, whenever you perform either of the following actions:

  • Create Job
  • Create Execution Task
  • Modify Job
  • Execute Against
  • Execute
 Click here to expand the complete list of jobs supported by this feature
  • NSH Script Job

  • Distribute CO Job

  • Deregister CO Job

  • Discovery Job

  • Virtual Guest Template Job

  • USP Job

  • Compliance Job

  • SCAP Compliance Job

  • Software Deploy Job

  • Virtual Infrastructure Job

  • Agent Install Job

  • Audit Job

  • Snapshot Job

  • File Deploy Job

  • BL Package Deploy Job

  • Batch Job

  • All Patching Jobs


This topic describes the following sections:

To enable messages to review the number of target servers in a job

Ensure that all your Application Servers and consoles are using version 8.9.02 or later. 

To enable messages in your console that display the number of target servers impacted by a job, run the following command in the blasadmin console and restart the Application Server:

set JobFactory ShowConfirmationOnTargetSelection true

Similarly, to disable the messages that display the target server count, run the following command in the blasadmin console and restart the Application Server:

set JobFactory ShowConfirmationOnTargetSelection false 

The default value of ShowConfirmationOnTargetSelection is false.

For information about starting the blasadmin console, see Starting the Application Server Administration console.

If you set the blasadmin parameter in any of the Application Server, it applies to all the other Application Servers in multiple Application Servers (MAS) environment.

Every time you Create Job, Create Execution Task, Modify Job, Execute Against, and Execute a job, a message with the number of target servers is displayed.

This job will execute against X target(s). Ensure that you assess the number of targets before you proceed.

You can then review the number of target servers, and decide whether you want to proceed or cancel the operation, depending on the impact.

To set the maximum number of target servers in a job 

NEW IN 8.9.04 Ensure that all your Application Servers and consoles are using version 8.9.04 or later. 

To set the maximum number of target servers, any job can run against, set the following parameters in the blasadmin parameter list under the JobFactory component:

  • LimitMaxTargetsInJob
  • MaxTargetsInJob

To set the parameters for job qualification check, execute the following commands in the blasadmin console and restart the Application Server:

set JobFactory LimitMaxTargetsInJob true
set JobFactory MaxTargetsInJob <number>

Similarly, to disable the option to set the maximum target server count, run the following command in the blasadmin console and restart the Application Server:

set JobFactory LimitMaxTargetsInJob false

The default value of the LimitMaxTargetsInJob option is false.

For information about starting the BLAS admin console, see Starting the Application Server Administration console. If you set the blasadmin parameter in any of the Application Server, it applies to all the other Application Servers in multiple Application Servers (MAS) environment. Also, you must restart all the Application Servers.

Every time you Create Job, Create Execution Task, Modify Job, Execute Against, and Execute a job, a message with the number of target servers is displayed. If you select the number of target servers (for example, Y) more than the count mentioned in MaxTargetsInJob (for example, X), you get the following error message:

Job cannot be created/edited/executed because Y server(s) are specified in the job. A maximum of X server(s) is allowed.

You can then review the number of target servers. The confirmation message is available only for interactive interfaces and not available for scheduled jobs and non-interactive interface (for example, BLCLI, SOAP, REST). For the non-interactive interfaces (BLCLI, SOAP, REST) or scheduled jobs, TrueSight Server Automation does not perform the check for the number of target servers.

If you want to change the limit of maximum target server count for a scheduled job, disable the LimitMaxTargetsInJobs parameter (set JobFactory LimitMaxTargetsInJob false), and then update the limit of maximum target server count.

To count the number of servers

When you set the maximum number of target servers in MaxTargetsInJob option, it calculates the unique count of the server. If the unique count exceeds the value specified in the MaxTargetsInJob option, the job is not created, modified, or executed.

The following example explains how the server count is calculated for MaxTargetsInJob option.

You set 250 as the value of the MaxTargetsInJob option.

While creating a job, you added 250 target servers to one group and added the same 250 target servers to another group. Although the cumulative count of the target servers is 500, the unique server count is 250. So, the job executes without any error message about the target count. For information about how to create a job, see Creating and modifying TrueSight Server Automation jobs.

While creating a Batch Job and using Use servers from individual jobs in Batch Job - Options, you added 30 individual jobs where each job is executed for 220 servers.  Although the cumulative count of the target servers is 6600 (30 jobs * 220 servers each), the target count for each job is less than the value specified in MaxTargetsInJob option (in the example, 250). So, the Batch Job executes without any error message about the target count. 

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

Comments