This section describes how to customize OMi, extend its functionality, and use APIs to perform operations. The intended audience are administrators and integrators who need to establish advanced configurations and extensions.

This section covers the following topics:

  • Develop content provides steps required for content developers to add management capabilities for a new application, using the fictitious ACME environment as a simple example. The example illustrates the various integration steps required in order to make management information of the new application available in OMi.

  • Populate the RTSM provides information for developers to create their own topology synchronization mapping rules, to augment the out-of-the-box mapping rules to populate the Run-Time Service Model (RTSM) with configuration items (CIs) and CI relationships from nodes and services in OM.

    The ACME environment example, introduced in Develop content, is developed further to illustrate how to create topology synchronization rules specific to a particular service model.

  • Event Processing Interface describes the role of event processing scripts and custom actions for modifying and enhancing events during event processing.

  • Integrate the OMi UI with other applications describes how to integrate parts of the OMi user interface with an external application using a drill-down URL launch.

  • Automate operator functions and event change detection provides integrators with information to allow them to programmatically automate operator functions and detect event changes using the Event Web Service. Everything that an operator can do in the console while working on events can be done programmatically, to improve efficiency.

    The main use case for the Event Synchronization Web Service interface is to synchronize events and changes to events with an external manager such as an ITIL incident manager, for example, HPE Service Manager or BMC Remedy Service Desk.

  • Integrate external event processes describes the Event Synchronization Web Service interface that enables integrations with external applications, where the aim is to integrate external processes into event processing. The interface enables notification of forwarded events and subsequent changes to be received programmatically.

  • Command-Line Interfaces describes command-line interfaces that are useful when managing Monitoring Automation configurations.

  • Web Service Interfaces describes several web services that allows integrators to automate OMi functions.

  • Groovy scripts describes how Groovy scripts are developed and deployed to implement customizations.

  • Service Health describes Service Health rules APIs and Service Health external APIs.