Use the information in this section to select and configure job types for the Operator-Initiated Change and Change-Initiated Job use case as well as incident generation upon job failure.
The following table provides information about job configurations for BMC Change Automation.
Supported job types | Description |
---|---|
Operator-Initiated Change (OIC) To run a job with change management approval | Use this configuration for job types that require change management system tracking and approval. When you run the job, a prompt to create a Request For Change (RFC) is triggered. The job undergoes change approval process prior to execution. |
Generate incident | Use this configuration to generate an incident if a job fails. |
Change-Initiated Job (CIJ) To create task template | Use this configuration to execute simple and routine jobs without involvement of operations team. For example, file deploy jobs. With this configuration, a task template corresponding to the job is created in BMC Remedy ITSM. This task template contains all the job details. |
The following table describes job types that can be configured for these use cases.
Job type | Change management approval | Incident creation | Task template creation |
---|---|---|---|
BLPackage Deploy Job
| |||
Batch Job | |||
File Deploy Job | |||
Network Shell Script Job | |||
Oracle Enterprise Linux Patching Job | |||
Provision Job | |||
Red Hat Linux Patching Job | |||
Software Deploy Job | |||
Solaris patching Job | |||
SuSE Linux Patching Job | |||
UCS Provision Job | |||
Virtual Guest Job | |||
Windows Patching Job | |||
Workflow Job |