Has anyone successfully integrated with Control M to auto create job failure tickets?

[daniellethomson]

Has anyone successfully integrated with Control-M? We are trying to auto create incidents from Control-M alerts, and then send that ticket number back to the Control-M console to remove the emergency status etc. I can't find any good documentation on how users have set this up in the past.

[David Katz]

Were you ever able to integrate with Control-M?  

[Binu4]

I am also looking for an answer to this.

We are running Control-M version 8 with latest fixpack now.

[Gianpaolo Pagan]

Hi there,

I haven't had the chance to work on that, but I can see in the Control-M EM API Documentation that you can list job statuses via API call or you could use the SNMP integration.

Easiest way - SNMP Integration:

1. In control-M you can enable snmp trap forwarding to an event management system
2. You can then set ServiceNow Event management as the destination, leveraging the SNMP trap listener.
3. In Control-M you have a file called BMC-CONTROLMEM-MIB.txt which is a SNMP MIB file you can load in ServiceNow Event Management to make it easier to parse the traps you receive.
4. Traps are then turned into events and alerts. You might need event rules to clean them up and make the events look like the way you want them.
5. You can then use the Out Of the box capabilities of event management to automatically open and update incidents from alerts so that they constantly keep the incidents updated.

A more complex option but gives more control over the integration flow:

Another way to handle this would be to build an event management connector that integrates with Control-M to create and update events and alerts.

You can then use the Out Of the box capabilities of event management to automatically open and update incidents from alerts so that they constantly keep the incidents updated.

The event management connector can be bi-directional, so the logic could call the Control-M api to update things back.

In order to get job status, you could use Job tracking (page 161):

Which among other things returns the status of active jobs with:

 Ended OK

 Ended not OK

 Executing

 Wait Condition

 Wait Resource

 Wait User

 Not in AJF

 Unknown

Or you could use Control-M BIM "Batch Impact Manager"  calls (page 184 of the Control-M EM API guide). It allows to "retrieve the list of services active in the Batch Impact Manager Server", on page 186 you can see what details about services and jobs are returned.

Building a connector requires of course specific skills, so you need to have access to someone able to do that.

In any case I hope this helps.

Gp

[Binu4]

Thank you Gianpaolo. Will give it a try.