IT Operations Management (ITOM)

OMi Management Pack Development Kit – Topology

OMi Management Pack Development Kit – Topology


Guest post by Devadoss, Madan Gopal - Expert at HP Software


In the HP Operations Manager i (OMi) world, IT infrastructure monitoring is primarily topology-centric. In simple terms, topology is a hierarchical tree representation of the monitored world that depicts the understanding of OMi on what is monitored. The monitored element types are referred as Configuration Types (CI Types). A topology tree consists of instances of different CI Types and the relationship between them. The topology information is stored in a central configuration management database called the Run Time Service Model (RTSM).

The OMi MP Development Kit or DevKit enables you to create OMi Management Packs, which are monitoring solutions built on the OMi incident management platform, in an easy and efficient manner. This blog delves into the topology submission aspect of the DevKit and explains how to submit an OMi RTSM topology using the DevKit APIs.

This blog is the third installment in a series of blogs on the DevKit. I strongly recommend that you go through prior blogs and videos of this series as well as the additional references listed at the end of this blog. Also, I have included a video in this blog to aid your understanding of this topic.

The topology information is submitted to OMi RTSM as an XML tree that adheres to a well-defined schema. Now, a number of relationship types are possible in the RTSM. However, in the real world scenario, over 90 percent of the relationships are addressed by only a handful of relationship types.


To submit a topology tree to OMi RTSM, you have to implement a Perl interface in the monitoring solution of name topology().


Inside the topology() method, you can discover the monitored application/domain using open Perl language capabilities and submit the information using simple Perl data structures.


The adjoining image illustrates how it is done. Relationships are defined using simple and intuitive English language words such as “requires”, “users”, “member of” and so on.


As a developer, you just need to populate a Perl hash with keys as depicted in the example and assign appropriate values to each entry. The job of converting this data structure in to an XML tree is performed by the DevKit.


If I have to suggest a one-stop destination for all these details, it is the OMi MP DevKit Developer Guide (see end of blog).


The DevKit layer that invokes the topology() method handles the information returned differently based on whether the execution is in standalone mode or in production runtime mode.


In the standalone development mode, the DevKit writes the topology XML to the console and you can certify the discovered topology from the information printed to the console.


The DevKit layer will automatically invoke the correct underlying APIs at runtime and submit the topology XML information to OMi RTSM.


This capability allows anyone with Perl programming skills to write the topology code without having to know the underlying product interfaces or implementations.





Watch this video to learn more about the concepts and technique of topology submission.








Don’t forget to review these related blog posts and documents for more information on the DevKit and on developing an OMi Management Pack.




Join the Operations Bridge team at HP Discover London to see a demonstration, get questions answered or just say hello.



  • operations bridge
0 Kudos
About the Author