Configuration Modeling with Objects in In-Memory Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing application configurations across diverse systems, especially in shared in-memory database systems and multi-tenancy environments, is challenging due to the need for concurrent adaptation by authors, partners, and customers, leading to incompatibilities and complexity.

Innovation Solution

A system and method for configuration management using a life-cycle approach in an in-memory database repository, where a base configuration is modeled, extended, and stored as repository objects, allowing for flexible customization and activation of delta configurations to create a merged runtime configuration, enabling efficient adaptation and compatibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a base configuration is modeled and stored as a repository object, then configuration management is simplified and compatibility is ensured, but the system complexity increases due to the need to model and manage multiple configuration extensions

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

Solution Approach 1:

The configuration is segmented into a base configuration (stored as a repository object) and multiple extensions (stored as separate repository objects linked to the base configuration). This segmentation allows the base configuration to be managed centrally while extensions can be added independently, simplifying configuration management operations while introducing structured complexity for handling variations.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If multiple configuration extensions are modeled and linked to the base configuration, then adaptability to different needs is improved, but the complexity of managing and evaluating configurations increases

Engineering Contradiction:
ImproveadaptabilityVSAvoidmanagement complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The configuration system is made dynamic by allowing multiple extensions to be linked to a base configuration, where each extension can be activated or deactivated based on specific needs. This dynamic structure enables the system to adapt to different requirements by selectively combining base configuration and extensions, while the lifecycle management approach provides structured control to manage the complexity of multiple configurations.

Inventive Principle:
Principle #15Dynamics

3Ease of manufacture

If configurations are managed using traditional methods, then implementation is simpler, but runtime evaluation complexities and incompatibilities arise in shared in-memory database systems

Engineering Contradiction:
Improveimplementation simplicityVSAvoidcompatibility
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The configuration model includes a validation phase that performs preliminary evaluation of configuration extensions against the base configuration before activation. This preliminary action identifies and resolves incompatibilities in advance, ensuring that only compatible configurations are activated in the runtime environment, thereby improving reliability while maintaining implementation simplicity through automated validation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9047105B2Configuration modeling with objects
Publication Date: 2015.06.02 SAP SE
  • US9047105B2 patent drawing
  • US9047105B2 patent drawing
  • US9047105B2 patent drawing

AI summary

A computer-implemented method, computer program product and system for configuration modeling with objects are disclosed. A base configuration of an application is modeled, to generate a configuration model that specifies parameters, types, structures, and boundary conditions of the base configuration of the application. The configuration model is stored in a database repository as a repository object that can be activated with configuration data. One or more extensions to the base configuration is modeled as one or more configuration model extensions. The one or more configuration model extensions are stored as repository objects linked to the repository object representing the configuration model.