Workload Change Manager integration with a change management system
You can integrate Workload Change Manager (WCM) with a change management system that manages the request tickets for the following actions:
Create a Ticket: The change management system creates the ticket automatically after the Web user sends the request, or the Web user creates the ticket from the change management system manually.
Change a Ticket State: The change management system changes the ticket state after the Web user or the scheduler changes the request state.
Show Ticket State: The change management system shows the state of the ticket after the Web user or the scheduler requests it.
To enable the REST API communication between WCM and the change management system, you must implement one of the following:
Dedicated REST Server: The REST server exposes the API according to the WCM requests, and then sends API requests for the change management system to create and update tickets. This integration requires you to create and maintain the REST server.
Directly: Some change management systems, such as Service Now, enable you to create and implement new APIs for integration with their external systems. WCM sends API requests directly to the change management system to create and update tickets, and you do not need the dedicated REST server. This integration requires you to create and implement the WCM API in your change management system.
For more information, see Integrating Workload Change Manager with a change management system.
Note: The Remedy example provides two actions; create and verify a Change Ticket ID and verifying approval of a request when it is submitted for approval. You can add more properties for the different Control-M Workload Change Manager request statuses; such as returned, rejected, etc. You can modify and add properties that suit your organizations' needs. You can also use the Remedy example as a basis to create your own Rest Service for a different change management system.
