Template-Based Configuration Architecture for Enterprise Software

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current enterprise software configuration methods are time-consuming, error-prone, and require sophisticated knowledge, with redundant system-dependent information distribution, making it difficult to adjust configurations and move them between systems, leading to inconsistent cluster node configurations.

Innovation Solution

A template-based configuration architecture that separates configuration levels, allowing for dynamic, system-independent changes and automatic adaptation to environment changes, using a three-level structure: default configuration, configuration templates, and system configuration, with parameterized and computed settings to ensure consistency across instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual configuration is used for each AS instance, then configuration can be customized, but the process is time-consuming and error-prone

Engineering Contradiction:
Improveconfiguration customizationVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The configuration is segmented into three distinct levels: default configuration level (system-independent settings), configuration template level (reusable patterns), and system configuration level (instance-specific settings). This segmentation allows automatic inheritance of common settings while enabling customization only where needed, dramatically reducing configuration time and errors.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Configuration templates are prepared in advance with pre-defined settings and patterns. These templates contain pre-configured parameters and relationships that can be automatically applied to multiple AS instances, eliminating the need for manual configuration of each instance from scratch.

Inventive Principle:
Principle #10Preliminary action

2Stability of the object's composition

If system-dependent information is statically configured, then configuration is fixed, but it cannot be adjusted when system settings change

Engineering Contradiction:
Improveconfiguration stabilityVSAvoidconfiguration adjustability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The configuration system transitions from static to dynamic by introducing computed settings that are calculated at runtime based on current system state. Configuration templates can be parameterized with system-specific values, allowing the same template to adapt to different system environments automatically without manual reconfiguration.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Configuration parameters are made changeable through the template system, where parameters can be defined as expressions or references to system properties. When system settings change, the parameters automatically update, enabling dynamic adaptation while maintaining configuration structure and consistency.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If configuration is copied between systems, then deployment is fast, but system-specific settings become inconsistent

Engineering Contradiction:
Improvedeployment speedVSAvoidconfiguration consistency
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

Configuration templates serve as reusable copies that can be applied across multiple AS instances and systems. Instead of copying complete instance configurations (which causes inconsistency), the template level captures the essential patterns and settings that can be safely replicated, while system-specific parameters are localized to prevent conflicts.

Inventive Principle:
Principle #26Copying

4Ease of manufacture

If default configuration is used for all instances, then setup is simple, but resource optimization is not achieved

Engineering Contradiction:
Improveconfiguration simplicityVSAvoidresource utilization
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The configuration system applies local quality by allowing different configuration strategies at different levels: default configurations provide simplicity at the system level, while configuration templates enable optimized settings at the instance level. This layered approach maintains ease of setup while achieving resource optimization through targeted customization.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9038023B2Template-based configuration architecture
Publication Date: 2015.05.19 SAP SE
  • US9038023B2 patent drawing
  • US9038023B2 patent drawing
  • US9038023B2 patent drawing

AI summary

A system and method are provided for template-based configuration architecture. Configuration information from a first level is inherited. Configuration templates are customized via the inherited configuration information based on usage at a second level. The customized configuration templates are applied to default instances at a third level.