Managing RFCs using the integration between HCL Workload Automation and Change and Configuration Management Database
About this task
Procedure
- After receiving the RFC, the Change administrator verifies the state of the workstations and the installed software in Change and Configuration Management Database. For the workstations which have the HCL Workload Automation agent installed, she usesDynamic Workload Console to check the number and status of jobs currently running.
- The Change administrator performs a launch in context of the Dynamic Workload Console. An instance of the Dynamic Workload Console is displayed, listing the jobs running on the selected workstation together with the related details.
- The Change administrator notifies the HCL Workload Automation administrator about the status of the jobs on the workstations and asks for instructions.
- The HCL Workload Automation operator uses the Dynamic Workload Console to stop or pause the jobs running on the affected workstations.
- The HCL Workload Automation operator notifies the Change Administrator that the jobs on the impacted workstations have been stopped or paused and that she can proceed with the patch installation.
- The Tivoli Provisioning Manager administrator starts Tivoli Provisioning Manager.
- The Tivoli Provisioning Manager administrator submits a workflow that implements the RFC.
- The Tivoli Provisioning Manager administrator checks with Tivoli Provisioning Manager that the patch has installed successfully on all workstations.
- The Tivoli Provisioning Manager administrator notifies the Change administrator that the installation operations have completed on all the affected workstations.
- The Change administrator closes the RFC.
- The Change administrator notifies the HCL Workload Automation administrator that the RFC has been closed.
- The HCL Workload Automation operator uses Dynamic Workload Console to restart the jobs that were stopped or paused on all the affected workstations.