Modular Configuration Logic for Application Server Modules

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In typical application server and cloud environments, the global configuration of application server modules requires reconfiguration whenever new modules are added, leading to memory and performance issues due to the need for a single central configuration file that must be modified and updated, which is inefficient and inflexible.

Innovation Solution

A system and method for providing configuration modularity that allows new modules to be added without modifying a global configuration file, by distributing default configuration data between modules and using a modular configuration logic that determines the configuration source for each module, including global, annotation-based, and default configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a single global configuration file is used to manage all application server modules, then centralized configuration management is achieved, but the system requires reconfiguration whenever new modules are added, leading to memory and performance issues

Engineering Contradiction:
Improvecentralized configuration managementVSAvoidmodule addition flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent divides the global configuration file into multiple module-specific configuration files, each managing configuration for a specific module. This segmentation allows each module to have its own configuration scope, enabling new modules to be added without modifying the global configuration file, thus resolving the contradiction between centralized management and adaptation flexibility.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If a single central configuration file is modified to add new modules, then all configuration data must be loaded and updated, but this increases memory usage and reduces performance

Engineering Contradiction:
Improvesystem configurabilityVSAvoidmemory usage
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts module-specific configuration data from the global configuration file into separate configuration files. When a module is added or modified, only its specific configuration file needs to be updated, not the entire global configuration file. This extraction reduces the amount of configuration data that must be loaded into memory, thereby reducing memory usage and improving performance while maintaining system configurability.

Inventive Principle:
Principle #2Taking out (Extraction)

3Adaptability or versatility

If the global configuration file is updated frequently to accommodate new modules, then configuration management becomes complex, but this increases maintenance difficulty and reduces productivity

Engineering Contradiction:
Improvemodule integration capabilityVSAvoidconfiguration maintenance ease
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent applies local quality by allowing each module to have its own dedicated configuration file with specific properties tailored to that module's requirements. This localized configuration approach means that changes to one module's configuration do not affect other modules, simplifying maintenance and reducing complexity. Third-party module developers can include their configurations in their own files without affecting the global setup, making the system more maintainable while preserving integration capability.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9898344B2System and method for providing configuration modularity in an application server, cloud platform, or other environment
Publication Date: 2018.02.20 ORACLE INT CORP
  • US9898344B2 patent drawing
  • US9898344B2 patent drawing
  • US9898344B2 patent drawing

AI summary

In accordance with an embodiment, described herein is a system and method for providing configuration modularity in an application server, cloud platform, or other environment. For example, in a cloud computing environment, application server modules, e.g., WebLogic Server or GlassFish modules, can be embedded within the environment to provide various cloud platform functionalities. In accordance with an embodiment, the system comprises a configuration modularity logic for use in determining, for a particular application or service deployment, a configuration of application, module or service components, including determining if a configuration is provided by a global or domain configuration, determining if annotations are provided by the particular application or service deployment for use in configuring the application, module or service components, and/or determining if a default configuration is provided for use with the particular application or service deployment.