Federated Configuration for Application Servers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computing environments, especially cloud environments, traditional domain configuration updates face issues such as missed network messages and blended configuration changes from multiple software layers, making it difficult to trace the origin of configuration settings.

Innovation Solution

A federated configuration system that derives a runtime domain configuration from a base configuration, configuration fragments, and pluggable configuration transformers, allowing each layer to contribute and track its changes, and operates on an in-memory representation to control server behavior.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional configuration update model is used with administration server coordination, then configuration changes can be propagated across domain, but network reliability issues cause missed messages and late file updates

Engineering Contradiction:
Improveconfiguration update deliveryVSAvoidnetwork coordination infrastructure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the configuration data from the centralized administration server model and places it directly in the runtime server's file system. Configuration files are copied to the server's runtime directory where they can be read locally without network coordination, eliminating the dependency on reliable network message delivery between administration server and running servers.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a configuration fragment as an intermediary mechanism. Instead of directly coordinating updates through the administration server, configuration changes are packaged as fragments that contain both the configuration data and metadata about its origin. This fragment serves as a self-contained intermediary that carries all necessary information locally.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If configuration changes from multiple software layers are blended together, then comprehensive configuration is achieved, but tracing the origin of configuration settings becomes difficult

Engineering Contradiction:
Improvelayered configuration supportVSAvoidconfiguration origin tracking
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent applies local quality by giving each configuration fragment distinctive metadata that identifies its origin layer. Each fragment contains information about which software layer it came from, allowing the system to maintain the blended configuration from multiple layers while preserving the ability to trace each setting back to its specific origin through the fragment's metadata.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent segments the configuration system into distinct configuration fragments, each representing a specific software layer's configuration contributions. Instead of blending configurations into a single undifferentiated mass, each layer's configuration is maintained as a separate fragment with identifiable metadata, enabling both comprehensive configuration aggregation and origin tracking.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If frequent configuration updates are read from persistent storage, then configuration accuracy is maintained, but performance impact increases

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidserver performance
Core Design Contradiction:
Manufacturing precisionVSProductivity

Solution Approach 1:

The patent applies preliminary action by copying configuration fragments to the runtime server's file system in advance, before they are needed. Configuration files are prepared and placed in the runtime directory during server startup or deployment, so that when the server needs to read configuration, it reads from the already-copied local files rather than accessing persistent storage repeatedly, thus maintaining accuracy while improving performance.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10868719B2System and method for federated configuration in an application server environment
Publication Date: 2020.12.15 ORACLE INT CORP
  • US10868719B2 patent drawing
  • US10868719B2 patent drawing
  • US10868719B2 patent drawing

AI summary

In accordance with an embodiment, described herein is a system and method for providing federated configuration in an application server, enterprise computing, or other computing environment. A runtime domain configuration associated with a server can be derived from a base configuration, one or more configuration fragments, and one or more pluggable configuration transformers. Each configuration transformer can operate upon or revise a config descriptor's in-memory representation, for example by adding, deleting, or changing configuration elements within that representation. The changes made to an in-memory working runtime configuration can then be used to control the operating configuration and behavior of the server.