Directory Services Integration Bridge for Heterogeneous Database Consolidation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Directory services databases from different vendors and versions often exhibit incompatibilities, leading to productivity losses, security risks, and management challenges due to the inability of software management tools to work across disparate implementations, causing frustration and inefficiencies in IT operations.

Innovation Solution

A system and method for directory services integration and replication that analyzes and consolidates multiple directory services databases into a unified structure, using configuration files and load/performance testing to create a merged schema and structure, adjusting indexes and schemas as needed, and utilizing custom adapters for replication, allowing for the coexistence and eventual decommissioning of legacy databases.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple directory services databases from different vendors are maintained separately, then vendor-specific functionality and compatibility are preserved, but administrative complexity and management difficulty increase

Engineering Contradiction:
Improvevendor-specific compatibilityVSAvoidadministrative complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a directory services bridge that acts as an intermediary between multiple directory services databases from different vendors. The bridge translates directory services protocols and data formats between heterogeneous systems, enabling unified management while preserving vendor-specific functionality. This mediator approach allows administrators to manage multiple databases through a single interface without losing compatibility with individual vendor implementations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The directory services bridge is designed with universal functionality to work with multiple directory services vendors and versions simultaneously. It implements multiple directory services protocols and provides a unified management interface that can administer heterogeneous directory services databases through a single system, reducing administrative complexity while maintaining broad compatibility.

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

2Productivity

If directory services databases are consolidated into a unified structure, then administrative capability and productivity improve, but structural incompatibilities and data loss risks increase

Engineering Contradiction:
Improveadministrative productivityVSAvoidstructural compatibility
Core Design Contradiction:
ProductivityVSManufacturing precision

Solution Approach 1:

The patent employs a migration planning tool that performs preliminary analysis of the source directory services databases before consolidation. The tool identifies structural incompatibilities, data mapping requirements, and potential data loss risks in advance. By performing these assessments beforehand, administrators can prepare appropriate migration strategies and data transformations, ensuring structural compatibility is maintained during the consolidation process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The directory services bridge and migration tools utilize parameter changes to adapt data structures during consolidation. The system transforms directory services data between different schemas and formats by modifying parameters such as object classes, attributes, and naming conventions. This parameter transformation capability allows heterogeneous directory services databases to be consolidated into a unified structure while preserving data integrity and structural compatibility.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If legacy directory services databases are decommissioned after consolidation, then system simplicity increases, but data recovery and rollback capabilities are reduced

Engineering Contradiction:
Improvesystem simplicityVSAvoiddata recovery capability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent implements a replication mechanism that creates and maintains copies of directory services data between the unified database and legacy databases during the transition period. This copying approach allows the system to simplify by consolidating management while preserving data in the legacy systems for recovery purposes. Administrators can replicate data bidirectionally, ensuring that if issues arise during consolidation, data can be recovered from the copied legacy databases.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The migration planning tool and replication mechanism provide beforehand cushioning by maintaining backup copies of directory services data in legacy databases during the consolidation process. This prior cushioning ensures that if the unified database structure proves incompatible or data loss occurs, administrators can rollback to the legacy databases and recover data, providing a safety buffer during the transition.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS8108349B1Directory services integration and replication system
Publication Date: 2012.01.31 T MOBILE INNOVATIONS LLC
  • US8108349B1 patent drawing
  • US8108349B1 patent drawing
  • US8108349B1 patent drawing

AI summary

A system for directory replication and integration is provided. The system comprises a computer system and an application, that when executed on the computer system, analyzes a first structure of a first directory services database and generates a plurality of configuration files based on the analysis of the first structure of the first directory services database. The system also creates a second structure using the configuration files and tests the second structure using load and performance profiles and adjusts the second structure based on the results of the tests. The system also replicates entries in first directory services database to a second directory services database according to the second structure.