Integrating BMC Control-M Workload Automation with ProactiveNet

Starting with BMC Service Resolution 3.5, you can integrate BMC Control-M Workload Automation with ProactiveNet. With this integration, it is possible to send BMC Control-M Workload Automation alarms as events to event management. Event management leverages service resolution functionality to create incidents in Remedy IT Service Management (Remedy ITSM).

This integration supports Level 1 of service resolution. For information about the service resolution levels, see BMC-Service-Resolution-levels.

The following topics are provided:

• • Benefits of the integration
  • Information flow
  • To integrate BMC Control-M Workload Automation with Event Management
  • Attribute mappings

Benefits of the integration

BMC recommends that you integrate BMC Control-M Workload Automation with Remedy ITSM through Event Management because of the following advantages:

• Provides support for Level 1 of service resolution.
• (With Event Management integrated with BMC Remedyforce) Enables creation of incidents for alarm events in BMC Remedyforce. This support is available only for Level 1 of service resolution.
• Due to integration with Event Management, alarm events can be made more context-aware by event filtering, enrichment, and custom mapping.
• Using the event-management policy, you can create incidents for major or minor alarm events.

Information flow

1. A BMC Control-M Workload Automation job fails and an alarm is raised.
   The alarm is converted to an event by mapping of appropriate attributes. See Attribute mappings.
2. The event is sent to a cell in Event Management.
3. The enriched event is then sent to Incident Management.
4. An incident is created for the alarm event.

To integrate BMC Control-M Workload Automation with Event Management

1. In the ctmticket/etc/ctmticket.properties file, perform the following actions:
   
   1. Set the value of the Integration_System parameter as follows:
      Integration_System=TrueSight
   2. Set CTMGUISERVER to point to the Control-M GUI server.
2. In the ctmticket/etc/ctmticket_TrueSight.properties file, set the following parameter values:

   1. Set the value of the BPPM_BASE_URL to point to the ProactiveNet Performance Management host name URL, for example:
      BPPM_BASE_URL = http://<Truesight_Host-name>/bppmws/api/.
      

      To integrate with another Event Management host, ensure that you delete the ctmticket/etc/cellDetails.properties file and enter the new host name in the ctmticket_TrueSight.properties file.

3. Verify that all of the following configurations are complete and have the correct values:

   Configuration	Required values or parameters
   ctmticket/etc/credentials.properties file	CONTROLMUSER CONTROLMPASSWORD TRUESIGHTUSER TRUESIGHTPASSWORD
   ctmticket/etc/ctmticket.properties file	CTMTICKETLOGDIR LOGLEVEL org.omg.CORBA.ORBClass=org.jacorb.orb.ORB org.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton com.bmc.ctmem.emapi.GSR.hostname com.bmc.ctmem.emapi.GAS.hostname com.bmc.ctmem.emapi.XMLDATAPATH
   ctmticket/etc/ctmticket_TrueSight.properties file	BPPM_BASE_URL points to the RESTful URI of the TrueSight/BPPM host.
   Control-M EM parameters	SendAlarmtoScript—Must be set to the path of the activation script in the bin directory: ctmticket.bat. For a Windows setup, a helper script called shortname.vbs provides the full path name in 8.3 format to be inserted into the Control-M parameter. SendSnmp—Must be given the value 1 or 2

Attribute mappings