Server Configuration Data Synchronization via Directory Service Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for updating server configuration data are either manual and labor-intensive or rely on a central configuration server, which can lead to inefficiencies and single points of failure in distributed computer networks.

Innovation Solution

A system where local server configuration data is stored and shared between directory service instances on multiple servers, allowing for synchronization and automatic updating of configuration data across the network, reducing the need for manual updates and minimizing central points of failure.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual update of server configuration data is performed on each server, then data consistency can be maintained, but administrative workload and time consumption increase significantly

Engineering Contradiction:
Improvedata consistencyVSAvoidadministrative workload
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent creates copies of configuration data stored in local databases on each server and synchronizes these copies across the network. This allows automatic distribution of configuration updates to multiple servers without manual intervention on each individual server, reducing administrative workload while maintaining data consistency through synchronized copying.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system enables servers to automatically update their own configuration data by synchronizing with the network. When configuration changes are made on one server, the self-service mechanism automatically propagates these changes to other servers through the synchronization process, eliminating the need for manual updates on each server while maintaining consistency.

Inventive Principle:
Principle #25Self-service

2Extent of automation

If a central configuration server is used to store shared configuration data, then automated updates can be implemented, but single points of failure and system complexity increase

Engineering Contradiction:
Improveautomated updatesVSAvoidsingle points of failure
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The patent segments the centralized configuration storage into distributed local databases on multiple servers. Each server maintains its own copy of the configuration data in a local database, eliminating the single point of failure associated with a central configuration server. The segmentation allows the system to continue operating even if one server fails.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges the functionality of centralized configuration management with distributed local storage by implementing synchronization between local databases. This combination allows automated updates to occur across the network while distributing the data storage responsibility across multiple servers, eliminating single points of failure.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If configuration data is stored locally on each server, then system performance and availability improve, but data synchronization and consistency management become more complex

Engineering Contradiction:
Improvesystem availabilityVSAvoiddata synchronization
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a feedback mechanism in the synchronization process where changes made to configuration data on one server are detected and automatically propagated to other servers. The system continuously monitors for changes and provides feedback by updating other servers' local databases, maintaining consistency across the distributed system without requiring complex manual coordination.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The synchronization mechanism acts as an intermediary between the local databases on different servers. It mediates the data exchange process by automatically detecting changes on one server and translating these changes into updates for other servers' local databases, simplifying the complexity of maintaining consistency across distributed storage locations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS7797412B2Method and system for managing server configuration data
Publication Date: 2010.09.14 ORACLE AMERICAN INC
  • US7797412B2 patent drawing
  • US7797412B2 patent drawing
  • US7797412B2 patent drawing

AI summary

A computer readable medium includes executable instructions for managing server configuration data by configuring a first server using local server configuration data, where the local server configuration data is stored on the first server and as shared server configuration data by a first directory service instance operating on the first server, synchronizing the first directory service instance with a second directory service instance operating on a second server, where the shared server configuration data is updated, and updating the local server configuration data using the updated shared server configuration data.