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 case||Description of activity|
|Script execution||NSH 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.
- Job execution framework
- Resource usage of Snapshot, Audit, and Compliance Jobs
- Resource usage of Component Discovery Jobs
- Resource usage of NSH Script Jobs
- Resource usage of Deploy Jobs
- Resource usage of Provision Jobs
- Resource usage of Patching Jobs
- Resource usage of Virtualization Jobs
- Resource usage of administrative jobs