Operator-initiated Change for BMC Remedyforce
This topic describes the Operator-initiated change Run Book, which integrates BMC Server Automation with BMC Remedyforce by using BMC Atrium Orchestrator.
When operations changes are implemented, operators need to record these changes in BMC Remedyforce Change Management. To automate this change tracking process, a change request is automatically created in BMC Remedyforce whenever a BMC Server Automation operator submits a job that requires BMC Remedyforce tracking and approval. After the change request is approved in BMC Remedyforce, the job is scheduled for execution in BMC Server Automation.
After the job is run, the BMC Remedyforce task linked to the change request is closed with an associated completion status and any changed configuration items (CIs).
The main benefit of this integration is to enforce continuous compliance to the change process without introducing labor intensive activities. The integration reduces the risk of unauthorized and unplanned changes through enforced change tracking.
To use the operator-initiated change for BMC Remedyforce run book
The following table provides an overview of the user tasks involved in this run book.
Description and reference
|Step 1: Create a File Deploy job||BMC Server Automation|
When you create a File Deploy job that requires BMC Remedyforce approval, you are prompted to select the approval type and enter the approval parameters when you configure the schedule. You can specify an approval type when you execute a job or schedule a job for execution.
For more information, see the BMC Server Automation online documentation.
|Step 2: Set the approval type||BMC Server Automation|
The Approval Information tab enables you to select an Approval type and enter the BMC Remedyforce parameters needed to create a new change ticket or use an existing one. On the Enter approval information dialog or the Approval Information tab, do the following:
For more information, see in BMC Server Automation online documentation.
|Step 3: Execute the Job||BMC Server Automation|
After the job definition is completed, BMC Server Automation schedules the job and requests that a new change request be created in BMC Remedyforce. A new change request is created using a specific change template and includes one task, even if multiple servers are used as targets. The change request ID and task ID are sent to the BMC Server Automation system. The servers that have been specified as targets are associated to the task in BMC Remedyforce .
You can verify whether the interaction with BMC Remedyforce is successful by reviewing the job schedule log, which is displayed under the job until the job starts running. For information, see Viewing job schedules in the BMC Server Automation online documentation.
|Step 4: Approve the change and task||BMC Remedyforce|
If you have selected the Manual Approval type for the job, you need to manually approve the change request and task in BMC Remedyforce.
To manually approve the change request:
If you have selected automatic or emergency approval type for the job, the change request status changes to APPROVED automatically and an email alert is sent to the specified user from BMC Remedyforce by using the Workflow Rule defined in BMC Remedyforce. After an email is received, the status is communicate to BMC Server Automation.
|Step 5: Verify the status of the job||BMC Server Automation|
After the change is approved, the job starts executing and the information in the job schedule log is rolled into job log.
The job is blocked until approval notification is received from BMC Remedyforce. The job displays a status of Waiting for Approval until the approval notification is received. When the approval is received, the job is executed automatically (for Execute now) or at the scheduled time (for scheduled jobs).
|Step 6: Review the status of the change request||BMC Remedyforce||After the BMC Server Automation job execution completes successfully, the BMC Remedyforce user opens the change ticket to review whether the status of the linked task is CLOSED and the change request is CLOSED.|