Population Adapter Modes

The UCMDB Adapter Framework allows two types of population adapters:

• Standard Population Adapter

  • Is characterized by the absence of the <changes-source/> tag in the adapter XML file
  • Will always bring the full query data from the external system. In this case, the UCMDB Probe Framework is responsible for determining the difference between two consecutive runs. The Probe Framework achieves this by comparing the previous result for the given query with the current result, and computing the differences. Full population is achieved by not comparing the current query result and treating it as the final result. This flow implies that the populated data is not filtered by a “from date”, because filtering by a date would render data comparison meaningless.

• changes-source Population Adapter

  • Is configured by the use of the <changes-source/> tag in the adapter XML file:

    

  • The changes-source adapter is responsible for computing the difference between two consecutive runs.

Deleting CIs when using a changes-source adapter

If you are using a changes-source population adapter, your adapter is responsible for explicitly deleting CIs. This is done by using the is-deleted mapping file XML attribute, which accepts a valid Groovy expression.

For example, in the mapping file shown below, the population connector returns Service instances. Although the instances are still valid, some CIs that were part of those Service instances were deleted. To signal the delete of those CIs, you need to use the is-deleted attribute on the BusinessService mapping.