UCMDB API Use Cases

The use cases listed in this section assume two systems:

• Universal CMDB server

• A third-party system that contains a repository of configuration items

This section includes the following topics:

Populating the CMDB

Use cases:

• A third-party asset management updates the CMDB with information available only in asset management

• A number of third-party systems populate the CMDB to create a central CMDB that can track changes and perform impact analysis

• A third-party system creates Configuration Items and Relations according to third-party business logic, to leverage the UCMDB query capabilities

Querying the CMDB

Use cases:

• A third-party system gets the Configuration Items and Relations that represent the SAP system by retrieving the results of the SAP TQL

• A third-party system gets the list of Oracle servers that have been added or changed in the last five hours

• A third-party system gets the list of servers whose host name contains the lab substring

• A third-party system finds the elements related to a given CI by getting its neighbors

Querying the Class Model

Use cases:

• A third-party system enables users to specify the set of data to be retrieved from the CMDB. A user interface can be built over the class model to show users the possible properties and prompt them for required data. The user can then choose the information to be retrieved.

• A third-party system explores the class model when the user cannot access the UCMDB user interface.

Analyzing Change Impact

Use case:

• A third-party system outputs a list of the business services that could be impacted by a change on a specified host.