Understanding job behavior

The use cases you can perform with BMC Server Automation require resources, such as CPU and working memory, at different levels, according to their function. The resource usage varies based on whether the main work of the use case is executed on a BMC Server Automation component (such as Application Server) or on a managed target.

The following table provides an overview of where the activity takes place for each major use case:

Use caseDescription of activity
Patch management
  • Analysis – Processing (and most workload) takes place on the targets based on the size/scope of the policy and patch metadata.
  • Deploy – Transfers payloads over network and installs them on targets.
Compliance
  • Analysis - Rules based assessment of each target in application server by pulling the necessary information from the target.
  • Remediation – Applies remediation scripts to all the non-compliant targets.
Script executionNSH Script Jobs invoke the actual NSH scripts in a separate process that can be created and managed either by the Application Server or by a separately-running application known as the process spawner.

The following topics provide an overview of the run-time behavior of BMC Server Automation job types, with an emphasis on computation, storage, and network resource requirements.

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

Comments