Hierarchical Configuration Object for Server Node Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The traditional two-tiered client-server architecture is inefficient for large enterprises due to its brittleness and complexity, particularly in managing and updating client-side applications, while the multi-tiered architecture, although more flexible and scalable, introduces significant network administration overhead.

Innovation Solution

A system and method for managing multiple server nodes by organizing them into groups with a central hierarchical configuration data object, allowing for simplified management through centralized storage and distribution of configuration data and binaries, enabling efficient startup and synchronization across instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multi-tiered architecture is implemented to improve flexibility and scalability, then adaptability is improved, but device complexity increases

Engineering Contradiction:
Improveflexibility and scalabilityVSAvoidnetwork administration overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

A centralized configuration server is introduced as an intermediary between administrators and the distributed multi-tiered system components. This server stores master configuration files and automatically distributes them to all nodes, mediating the complexity of managing multiple servers and databases while preserving the architectural flexibility and scalability benefits.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The configuration server performs multiple functions: storing configuration data, distributing configuration files to nodes, verifying integrity, and managing updates across the entire system. This multi-functional approach consolidates administrative tasks into a single system that handles diverse configuration management needs.

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

2Speed

If configuration data is stored locally on each server to improve access speed, then speed is improved, but reliability decreases

Engineering Contradiction:
Improveconfiguration access speedVSAvoidconfiguration data consistency
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system creates and distributes copies of the master configuration file from the centralized configuration server to all server nodes. Each node maintains a local copy for fast access during operation, while the configuration server retains the authoritative master copy. This ensures both rapid local access and consistent, reliable configuration data across the distributed system.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system implements verification mechanisms where nodes report back to the configuration server about their configuration status and integrity. This feedback loop allows the centralized server to monitor and ensure all nodes have correct, up-to-date configuration data, maintaining reliability while allowing local caching for speed.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7533163B1Startup framework and method for enterprise computing systems
Publication Date: 2009.05.12 SAP SE
  • US7533163B1 patent drawing
  • US7533163B1 patent drawing
  • US7533163B1 patent drawing

AI summary

A system and method for managing a plurality of sever nodes. In one embodiment, the sever nodes are organized into groups referred to as “instances.” Each instance includes a group of redundant sever nodes and a dispatcher for distributing service requests to each of the sever nodes. In one embodiment, a hierarchical configuration data object is stored within a database and is centrally accessible by all of the servers from all of the instances. The hierarchical configuration data object organizes configuration data and binary data in a manner which simplifies sever node management in a large enterprise network. For example, in one embodiment of the invention, when starting up servers and dispatchers within an instance, the server layout of the instance is retrieved from the hierarchical configuration data object. In addition, binaries and configuration parameters stored locally on the servers/dispatcher are initially compared with the binaries and configuration parameters stored within the hierarchical configuration data object. If the binaries and configuration parameters stored locally are out-of-date, then new binaries/parameters are downloaded from a central database.