Integration [716] - CI Synchronization (APM - UCMDB)

How Data is Synchronized Between APM and UCMDB
When referring to the concept of data information, it is important to distinguish between a UCMDB
CI (Configuration Item) and an APM entity. Both are defined in a different Data Model, and
there must be a conversion before transferring CIs in UCMDB to Applications in APM.

The following graphic shows the high-level components of the integration:

UCMDB stores its information using CIs. The integration chooses which data to pull from UCMDB
by defining integration TQL queries. Each TQL query defines a superset of data relevant for the
integration.

The UCMDB Push Engine:

• Retrieves the required data from the UCMDB, using the given TQL query.
• Filters the data to include only the data that has changed since the last execution of this synchronization.
• Splits the data into multiple chunks without breaking consistency.
• Sends the information to the Probe/Adapter.

The Push Adapter is a generic framework for easily configuring push adapters, using only XML and
Groovy. It allows easy mapping of the data from the UCMDB data model into the HP APM data
model, and the transfer of this converted data into the HP APM database through REST APIs
called from HP APM.