Configuration Model Transport with Delta Compensation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing software solutions face challenges in consistently managing and updating configuration states across different system landscapes, such as development, testing, and production environments, during the software lifecycle, leading to inconsistencies and potential failures in configuration actions.

Innovation Solution

A computer-implemented method that retrieves a predefined configuration model, compares it to existing configuration data, generates deltas, determines and executes configuration actions to update the configuration states, and includes compensation actions for failed executions, ensuring consistent transport of technical and business configuration data across system landscapes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration management is used across different system landscapes, then flexibility in individual environment configuration is maintained, but configuration consistency and reliability deteriorate

Engineering Contradiction:
Improveconfiguration consistencyVSAvoidconfiguration management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses templates to create standardized configuration models that can be copied and applied across multiple system landscapes. These templates define the structure and content of configuration items, ensuring consistency when deployed to different environments (development, testing, production) while eliminating manual configuration errors.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-defining configuration models and templates before actual deployment. Configuration items are prepared in advance with proper validation rules and dependencies established, so that when deployed to target systems, the configuration is already optimized and consistent across landscapes.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If configuration actions are executed without validation, then deployment speed is improved, but configuration errors and system failures increase

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration deployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements feedback mechanisms through validation rules that automatically check configuration items against predefined criteria during the deployment process. The system provides immediate feedback on configuration errors, dependency issues, and compliance violations, allowing for real-time correction without manual intervention while maintaining deployment speed.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system prepares compensation actions in advance that can automatically recover from configuration failures. If a configuration action fails validation or execution, pre-defined compensation mechanisms are triggered to rollback changes or adjust the configuration, cushioning against potential system failures while maintaining overall deployment integrity.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If comprehensive validation and testing are performed on configuration actions, then configuration reliability is improved, but processing time increases

Engineering Contradiction:
Improveconfiguration validation accuracyVSAvoidconfiguration deployment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies partial validation by performing different levels of checking based on the configuration item type and target system criticality. Essential validation rules are applied to all configurations, while more comprehensive testing is performed only on critical systems or high-risk changes, optimizing the balance between validation thoroughness and deployment efficiency.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS8572565B2Central configuration and transport supporting software lifecycles
Publication Date: 2013.10.29 SAP SE
  • US8572565B2 patent drawing
  • US8572565B2 patent drawing
  • US8572565B2 patent drawing

AI summary

Implementations of the present disclosure provide computer-implemented methods including retrieving a predefined configuration model from a plurality of predefined configuration models electronically stored in a configuration repository, the predefined configuration model providing predefined configuration data for a particular software application, comparing the predefined configuration data to existing configuration data of one or more target systems to generate a first delta, a first system landscape including the one or more target systems, determining one or more configuration actions based on the first delta, and executing the one or more configuration actions to update a configuration state of the one or more target systems from an initial configuration state.