An entity in CMDB responsible for retrieving or updating data in a remote system (data that is not saved in the Universal CMDB database). The adapter is aware of how specific data is modeled and knows the vendor-specific protocol for communicating with the repository. An adapter can be used either for setting up integrations (integration adapter) or for performing discovery tasks (discovery adapter).
The application module that enables you to manage the adapters needed to run discovery or set up integrations.
A calculated relationship represents the connection between the source and target CI, whose path meets the conditions defined for the triplets on which it is based in the CI Type Manager. The direction of the calculated relationship is not always the same direction as the physical relationship taken from the CI Type model. You can use calculated relationships to create TQL queries just like any other relationship in the CI Type model. This enables you to base Enrichment rules, Impact Analysis rules, and views on calculated relationships.
A tool used in various applications for displaying, managing, and searching within the CI views.
The central CMDB server and the authority for configuration management in the multiple CMDBs solution.
Represents a path in the topological graph. You use a compound relationship to define the allowed steps in the path between a source and target CIs.
A component of the CMDB that represents a physical or logical entity in the system. For example, CIs can represent hardware, software, services, or business processes. The CIs are organized into a hierarchical format based on the dependencies in your organization’s IT environment.
The category for each configuration item (CI). Each CIT provides a template for creating the CI and its associated properties.
Enables you to view the information in the CI Type model, which contains the definitions of all configuration item types (CITs) defined in the system and the relationships that define the connections between them. Each CIT has its own attributes, as well as the attributes inherited from its parent CIT.
The core information repository of HP Universal CMDB. The CMDB stores and handles the infrastructure information as CIs and relationships.
The user names and passwords provided by the user to enable Data Flow Management to connect to remote systems.
The flow of information, either into the CMDB or outwards to an external repository.
The management capabilities provided by the CMDB to control data flows.
The main data flow component responsible for requesting tasks from the HP Universal CMDB server, executing them, and sending the results back to the CMDB. The Probe includes two components: the Probe Gateway and the Probe Manager. The Gateway provides communication (http or https) between the Manager and the CMDB, for processes such as downloading tasks and returning task results. The Manager executes the task provided by the CMDB. The Gateway communicates with the Manager using RMI. One Gateway can connect to several Managers. By default, the Manager and the Gateway run as one process.
The application module that enables you to configure Probes and credentials.
The application module that enables you to view current information on all active jobs running on the Probes.
A data flow of type Data Push sends information from the CMDB outwards to an external system.
A UCMDB data source represents a possible source of information for the UCMDB TQL engine. A data source can be either the CMDB itself (including all the data populated into it by either discovery or integrations), or any integration of type Federation.
The mechanism that enables you to collect information about the IT infrastructure resources on your system and their interdependencies.
An adapter that is used by Data Flow Management to collect information about the IT infrastructure resources on your system and their interdependencies.
The application module that is used to control the discovery process. Using the Discovery Control Panel, you can select which discovery jobs to activate, as well as track the ongoing discovery process.
Discovery jobs are based on discovery adapters, and may override parameters, scheduling information, and trigger TQL assignments. All customization resides in the job, which means that one adapter can be used for different schedules and with different parameters.
A set of parameters that defines when discovery jobs are allowed to run.
One or more discovery jobs that together enable the discovery of a specific technology or application.
Communication credentials that are used to establish connections with remote systems such as SNMP, WMI, SSH, Telnet, and so on.
A logical term for a customer site where each IP address is individual, that is, each domain must contain unique IP addresses. There are two types of domains: customer, for a specific customer site that contains private IP addresses; external, for the Internet (public) domain that contains all the IP addresses that are not included in the customer site.
A class defined in the HP Universal CMDB data model whose instances are stored in external data repositories and not in HP Universal CMDB.
Represents an external data repository from which UCMDB is capable of federating data. Federated data sources are created within the Integration Studio by setting up Integration Points of type Federation.
The ability of the CMDB to bring in data from external data sources. That is, the data is not stored in the CMDB, but remains in the external data source. Each time the data is queried, UCMDB brings the data on the fly to the CMDB from the external data source.
Represents the limits defined for different operations in the system.
A unique CI ID, generated by the CMS, that identifies that CI throughout the system, making it easier to work in multiple CMDB environments.
Hardening guidelines provide the configuration information required to implement a more secure (hardened) HP Universal CMDB platform. For details on these guidelines, refer to the HP Universal CMDB Deployment Guide PDF.
The hierarchy of a view defines the organizational structure of CIs in the topology map, by displaying selected CIs at different levels (layers). When no hierarchy rules are defined, the topology map displays all CIs included in a query result on one level. For example, if a query result includes a CI and its child, both CIs are displayed on the same layer in the topology map.
HP’s solution for real-time performance and availability monitoring from a business perspective, service level management, end-user management, system availability management, and custom reporting.
CITs that inherit the attributes and behavior (such as the label function) of the parent CIT.
A UCMD integration enables the setting up of data flows, either from the CMDB to some external system (data push) or from an external system into the CMDB (population/federation).
An adapter that is used to integrate CIs and relationships between the CMDB and external data repositories. Available integration flows are population, federation, and data push.
Part of the CMDB, responsible for holding the CIs and the relationships between the CIs. The IT universe model is organized into a hierarchical format that represents your organization’s IT environment.
A portal that displays the operations and properties of all active, registered MBeans as a web interface, using HTML controls.
A set of parameters that defines when discovery jobs are allowed to run.
A component in the federation flow that connects CIs from different data repositories, when those data repositories are connected with a virtual link. By default, the connection is made using the UCMDB reconciliation engine.
An XML file used by integrations in UCMDBRTSM to map CI and Relationship types in UCMDB to CI and Relationship types in a target data store.
The process of mapping the complex relationships between servers, network, storage, and software, and logical elements such as business services, VPNs, and end users.
One or more discovery jobs that together enable the discovery of a specific technology or application.
An artificial entity defined in an adapter for reconciliation. For example, if reconciliation is done by a host CI, a host multinode is defined and all fields used for reconciliation are mapped to columns in the database.
A subset of resources defined by certain criteria, logically grouped together, which is used to add content to the CMDB. This content can include the discovery of IT infrastructure, integrations, CITs, views, and so on.
The application module that is responsible for dispatching user or system requests for resource operations such as export, import and delete. It enables you to deploy some or all of a package’s resources to the CMDB from your local directory, as well as export some or all of a package’s resources in the Package Manager to your local directory.
Packages and their resources are modeled in the CMDB as instances of CI types: "deployedpackage" and "deployedresource".
Each entity available in HP Universal CMDB is a CI type, TQL query, view, report, impact rule, discovery job, adapter, or schedule.
In terms of the Package Manager, a subsystem is a logical type of resource such as: class model, data model, view, type definition, discovery job, and so on.
Enables a query to the CMDB by defining topology query language (TQL) queries.
A pattern to be applied to a model or a collection of CIs to create a perspective based view using the Modeling Studio.
A data flow of type Population populates information from some external system as CIs and relationships, which are stored and managed within the CMDB.
Communication credentials that are used to establish connections with remote systems such as SNMP, WMI, SSH, Telnet, and so on.
The process of resolving data conflicts, either by resolving to a common naming schema or resolving data overlap differences within the records to a single answer. Reconciliation is composed of two parts: the first is identification of the CIs and relationships according to data entering the CMDB, and the second is the decision taken of which reported data is to be considered authoritative, in case of data conflicts (reconciliation priority).
Applications, databases, network devices (hardware and software), and servers that are discovered and managed by HP Universal CMDB.
A graph that represents additional TQL query data related to a specific CI.
An application that enables administrators to view performance and availability statistics for, and to manage the workload of, the HP Universal CMDB server, data processors, load balancers, and data collectors and the services they are running.
A TQL result that describes CIs and the relationships between them (graph result).
A language and tool for discovering, organizing, and managing IT infrastructure data. It is used to create queries that retrieve specific data from the CMDB and display that data in a graphical manner. TQL enables you to draw conceptual relationships between CIs and create visual images of IT infrastructure resources.
A CI (or set of CIs) that is used as a trigger to create a task from a discovery job.
A node can be defined as a trigger node in Impact Analysis Manager. Impact Analysis Manager enables you to simulate how infrastructure changes you want to make impact your system. A node defined as a trigger node is the root cause node, or the node that represents the changes you want to make to the system.
A TQL query that is assigned to a discovery job and automates the process of adding trigger CIs to that job.
The allowed steps in a path in a topology graph leading from the source CI to the target CI when creating a subgraph definition, a compound relationship, or a calculated relationship.
HP Universal CMDB provides procedures and recommendations to enable you to upgrade your platform to the latest version with the minimum possible interruption to your system and operations. For details, see the HP Universal CMDB Deployment Guide PDF.
A collection of CIs and relationships represented by icons. These CIs and relationships are the result of a TQL query to the CMDB, and are displayed as a view according to display and organizational rules that are assigned to them. Each CI/relationship can be presented in multiple views or by multiple icons in different view layers.
A relationship between two graph nodes that come from different data repositories. The instances of these relationships do not exist in any data repository and are created during TQL calculation.