This topic provides information about prerequisites and basic configurations to enable Operator-Initiated Change capability.
In Operator-Initiated Change, automation jobs that require approval from the change management system are tracked and run with the approval from the change management system.
Ensure the following prerequisites are met before enabling this capability:
Use information provided in the following table for successful implementation of the Operator-Initiated Change.
Stage | Description |
---|---|
1.Configure job types for OIC use case | In BMC Server Automation, select the Approval Required? check box for the configured job type. This is an essential configuration to create a Request For Change (RFC) before you run a job. After a job type is configured for OIC, an RFC is created for every instance of the job. Warning If you do not configure a job type for Operator-Initiated Change, an RFC is not created for the job. For detailed step-by-step instructions and information about supported job types, see Selecting and configuring supported job types. |
2.Create a Request For Change | Create a Request For Change by entering all the details for the request in Change Request Information dialog box. If you are integrating with an external automation system, you need to use the web service CHG_ChangeServiceInterface and provide inputs for mandatory details. |
3.Enable check box for ITSM approval every time that you run the instance of a job | Select the Execute on Approval in the Schedules panel of the job and specify approval parameters.
For details about setting up approval parameters, see Executing a job with BMC Remedy ITSM approval in BMC Server Automation 8.9 online documentation. |
1 Comment
Peter Lowater
It needs to state somewhere on this page
If "Approval Required" is enabled for a Job Type, then when a Smart/Static group is added to that job, the individual servers for the selected groups will be added and not the actual Smart/Static group