Centralized Server Configuration Management with Automatic Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current server management technologies lack a cohesive methodology for systematic and comprehensive management of servers in a server farm, particularly in maintaining synchronized configuration data across multiple servers, and fail to provide a centralized, extensible mechanism for storing application settings.

Innovation Solution

An extensible and automatically replicating configuration management infrastructure with a centralized configuration database and a configuration management object model that allows third-party updates without modifying the underlying schema, coupled with a secured synchronization mechanism using agents to ensure all servers are updated with configuration changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Stability of the object's composition

If configuration files are copied among servers to keep them in sync, then configuration consistency is improved, but additional manual work and complexity increase

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidmanagement complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

A centralized configuration database serves as an intermediary between servers and configuration data. The database manager on each server communicates with this central database to retrieve and synchronize configuration information, eliminating the need for manual file copying and reducing management complexity while maintaining configuration consistency across all servers.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Configuration data is automatically copied from the centralized configuration database to local configuration databases on each server. This automated copying process replaces manual file distribution, ensuring all servers receive updated configurations without requiring manual intervention, thereby improving consistency while reducing operational complexity.

Inventive Principle:
Principle #26Copying

2Ease of operation

If a centralized configuration database is implemented, then configuration management is simplified, but system complexity increases

Engineering Contradiction:
Improveconfiguration managementVSAvoidsystem architecture
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The configuration management system is segmented into distinct functional components: a centralized configuration database for storage, database managers on each server for communication, and local configuration databases for caching. This segmentation allows each component to perform its specific function independently, simplifying operation while managing system complexity through modular architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The centralized configuration database serves multiple functions: storing configuration data, providing synchronization service to all servers, and enabling automatic updates. This multi-functionality consolidates what would otherwise require multiple separate systems into a single universal configuration management solution, improving ease of operation without proportionally increasing system complexity.

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

3Adaptability or versatility

If application settings are stored in separate files, then application independence is improved, but synchronization difficulty increases

Engineering Contradiction:
Improveapplication independenceVSAvoidsynchronization difficulty
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

Individual application configuration files are merged into a unified centralized configuration database that manages all configuration data across the server farm. This consolidation maintains application independence through structured data organization while automatically synchronizing all configuration information, eliminating the synchronization difficulties associated with managing separate files across multiple servers.

Inventive Principle:
Principle #5Merging (Combining)

4Reliability

If configuration data is manually updated on each server, then system control is improved, but time consumption increases

Engineering Contradiction:
Improvesystem controlVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Configuration changes are prepared and stored in the centralized configuration database in advance before being automatically distributed to all servers. This preliminary action allows configuration updates to be staged and validated centrally, then automatically propagated to all servers simultaneously, maintaining system control while dramatically reducing the time required compared to manual updates on each server.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where database managers on each server communicate with the centralized configuration database to retrieve updates and report status. This feedback loop ensures configuration changes are reliably propagated and applied across all servers, maintaining system control through automated monitoring and reducing update time through efficient communication protocols.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP1899862B1Extensible and automatically replicating server farm configuration management infrastructure
Publication Date: 2018.02.21 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP1899862B1 patent drawingFigure 1
  • EP1899862B1 patent drawingFigure 2
  • EP1899862B1 patent drawingFigure 3

AI summary

An extensible and automatically replicating server farm configuration management infrastructure is provided. A centralized configuration database stores all configuration data for the server farm. New configuration data can be added to the configuration database by extending a configuration object model without knowing or changing the schema of the configuration database. A synchronization mechanism is provided for each server in the server farm to automatically keep configuration data in the server farm synchronized across multiple servers in the server farm.