Creating a customized content pack for Omi

The Extensibility guide describes how to validate the mapping rules using an XML schema.

The Extensibility guide explains the creation of a complete topo sync package using an example.

NOTE : This guide does not describe uCMDB basics and relies on quite some uCMDB know-how. (E.g. what are ci-types, what are the key attributes, etc.). The OMi Extensibility guide is the right place to describe these uCMDB basics.

Creating custom Content Pack requires uCMDB know-how, therefore it’s hard or even impossible to create a SyncPackage, if one doesn’t know what to map where.

It’s possible to map configuration item types to RTSM views using the RTSM Modeling Studio, so that views are available for selection and use in the Health Top View pane.

Comprehensive details about how to create new CI types, and how to work with the concepts of the RTSM, are described in the HP Business Service Management Modeling Guide.

This guide (Modeling.pdf) is part of the standard BSM documentation.