Federated CMDB MDR Registry Using UDDI

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current CMDB Federation standards lack implementation features for managing and integrating data from multiple Management Data Repositories (MDRs) into a seamless, unified view, particularly in registering MDRs, querying their data models, and defining attribute mappings for reconciliation.

Innovation Solution

A method and system for federating MDRs using a UDDI registry to register MDR services, query their data models, and map attributes from MDR data models to CMDB data models, enabling transparent data transfer and reconciliation, with push-mode and pull-mode architectures for data federation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data from multiple MDRs is integrated into a unified CMDB view, then data quality and reliability improve, but system complexity increases due to the need for registration, querying, and mapping mechanisms

Engineering Contradiction:
Improvedata qualityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a UDDI registry as an intermediary component that mediates between multiple MDRs and the CMDB. The registry stores interface information for MDR services and enables the CMDB to discover and manage MDR endpoints without direct complex point-to-point connections. This intermediary layer simplifies the overall system architecture while maintaining data quality across multiple sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data federation functionality into distinct modular components: (1) UDDI registry for storing MDR interface information, (2) query mechanism for retrieving MDR data models, (3) mapping mechanism for attribute transformation, and (4) reconciliation process for data integration. This segmentation allows each component to be independently managed and maintained, reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If MDR services are registered and managed through a UDDI registry, then ease of operation improves, but device complexity increases due to additional registration and management infrastructure

Engineering Contradiction:
Improveease of operationVSAvoiddevice complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent leverages the existing UDDI registry infrastructure, which is a universal standard for web service registration and discovery. By using this pre-established universal registry system, the patent avoids building a custom registration mechanism from scratch, thereby reducing device complexity while improving ease of operation through standardized interfaces and procedures.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If attribute mappings are defined from MDR data models to CMDB data models, then adaptability improves, but loss of information increases due to transformation and reconciliation processes

Engineering Contradiction:
ImproveadaptabilityVSAvoidinformation loss
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent implements attribute mapping that transforms data parameters from MDR data models to CMDB data models while preserving essential information. The mapping mechanism allows flexible parameter transformation including one-to-one mappings, one-to-many mappings, and many-to-one mappings, enabling adaptability between different data models while maintaining data integrity through structured transformation rules.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8380749B2MDR federation facility for CMDBf
Publication Date: 2013.02.19 BMC HELIX INC
  • US8380749B2 patent drawing
  • US8380749B2 patent drawing
  • US8380749B2 patent drawing

AI summary

This disclosure relates generally to the field of federated configuration management databases (CMDBs). To claim compliance with the CMDBf Standard (“the Standard”), a CMDB implementation must provide working and interoperable implementations of the interfaces defined in the Standard. To make a working implementation, certain non-obvious features are required that are not addressed by the Standard. Among these requirements are: registering management data repositories (MDRs) so that they can be federated; managing/maintaining the list of federated MDRs; querying an MDR for its Data Model; using such MDR Data Models to define mappings of one or more attributes from the MDR data model to one or more attributes of one or more of the CMDB's data models; identifying attributes and defining rules to be used when reconciliation is performed; and managing as well as storing data representative of those mappings. This disclosure addresses these and other deficiencies.