Transport Request Verification for Cloud Configuration Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud-based software applications face deployment issues due to configuration discrepancies between development and production systems, leading to errors when customizations are transferred, as dependent data required for functionality may be absent or incorrectly removed from transport requests.

Innovation Solution

A system and method for verifying transport requests before deployment, using a data dictionary to identify missing dependent data, and requesting corrections from the development system to ensure all necessary data is included, thereby preventing errors and ensuring successful deployment of customizations to the production system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If customization is deployed from development system to production system, then application functionality is enhanced, but deployment errors occur due to configuration discrepancies and missing dependent data

Engineering Contradiction:
Improveapplication functionalityVSAvoiddeployment success
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system performs preliminary verification of transport requests before deployment by checking for dependent data requirements using a data dictionary. This advance checking prevents deployment errors by identifying missing data (such as currency definitions required for exchange rate tables) before the customization is actually deployed to the production system.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A data dictionary serves as an intermediary between the transport request and the production system. It stores information about data dependencies and is used to verify whether required dependent data is present in the transport request, thereby mediating the deployment process and preventing errors.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Manufacturing precision

If transport request verification is performed, then deployment accuracy is improved, but processing time increases due to error checking and correction cycles

Engineering Contradiction:
Improvedeployment accuracyVSAvoidprocessing time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The verification process is performed preliminarily before actual deployment, using a data dictionary to quickly check for dependent data requirements. This approach identifies issues early in the process, preventing costly deployment failures and reducing overall processing time by avoiding iterative correction cycles.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If dependent data validation is implemented, then data completeness is ensured, but system complexity increases due to verification mechanisms

Engineering Contradiction:
Improvedata completenessVSAvoidsystem complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The data dictionary acts as a centralized intermediary that stores all information about data dependencies in a structured manner. It simplifies the verification process by providing a single source of truth for checking whether dependent data is present, rather than implementing complex verification logic throughout the system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11327743B2Transportation of configuration data across multiple cloud-based systems
Publication Date: 2022.05.10 SAP SE
  • US11327743B2 patent drawing
  • US11327743B2 patent drawing
  • US11327743B2 patent drawing

AI summary

A method for transporting configuration data may include determining that a customization created at a development system for a software application is being deployed at a production system hosting the software application. In response, a transport request including the customization may be verified to determine whether errors are present in the transport request. The errors may include dependent data that is required to deploy the customization at the production system being absent from the transport request. If errors are present in the transport request, a request for a corrected transport request may be sent to the development system. The customization included in the corrected transport request may be deployed at the production system by applying, to a configuration of the software application, the customization included in the corrected transport request. Related systems and articles of manufacture, including computer program products, are also provided.