Multi-Tiered Application Cloning via Dynamic Configuration and Token Status

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database and application refresh and cloning processes are time-consuming, lack standardization, and are prone to errors due to manual intervention, which affects the frequency and accuracy of data replication and can have significant implications for business operations.

Innovation Solution

A method and system for cloning a multi-tiered application that involves validating source and target server configuration data, dynamically generating configuration files, and using tokens to communicate status, allowing for automated sequential actions across nodes without human intervention, ensuring identical replication and reducing errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual editing of configuration files is performed during database and application refresh, then the process can be customized to specific needs, but the process becomes time-consuming and error-prone

Engineering Contradiction:
Improvecustomization capabilityVSAvoidrefresh time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent pre-generates template configuration files with placeholder values before the refresh process begins. During refresh, the system automatically substitutes actual values into these pre-prepared templates, eliminating the need for manual editing while maintaining customization capability. This preliminary preparation of configuration structures resolves the contradiction by having the adaptive framework ready in advance, allowing rapid automated population during execution.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service through automated configuration file generation and validation. The refresh process automatically creates, populates, and validates configuration files without human intervention, using predefined templates and automated value substitution. This self-service mechanism eliminates manual editing time while preserving customization through the template-based approach, directly resolving the time vs. adaptability contradiction.

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If manual editing of configuration files is performed during database and application refresh, then specific customizations can be made, but inconsistencies between different refreshes occur

Engineering Contradiction:
Improvecustomization capabilityVSAvoidconsistency between refreshes
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent establishes a standardized template structure for configuration files before refresh operations begin. These templates define the exact structure, required fields, and validation rules that must be followed. By pre-defining this framework, the system ensures that every refresh operation follows the same consistent pattern, eliminating variations and inconsistencies between different refreshes while still allowing customization through template parameters.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enforces homogeneity by requiring all configuration files to conform to standardized templates with uniform structures, field names, and validation rules. This standardized approach ensures that configuration files across different refresh operations are homogeneous in structure and content quality, eliminating inconsistencies. The template-based methodology maintains this homogeneity while allowing controlled customization through parameter substitution.

Inventive Principle:
Principle #33Homogeneity

3Productivity

If automated cloning processes are implemented, then time and effort are reduced, but complexity of the system increases

Engineering Contradiction:
Improverefresh frequencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the configuration management system into distinct modular components: template definition modules, value substitution modules, validation modules, and execution control modules. Each component performs a specific function independently, making the overall automated system easier to understand, maintain, and debug. This segmentation reduces the perceived complexity while enabling sophisticated automated cloning capabilities that significantly improve refresh frequency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system introduces configuration templates as intermediary artifacts between the automated cloning process and the final configuration deployment. These templates serve as a simplified interface that mediates between the complex automated substitution and validation processes and the final configuration output. This intermediary layer abstracts the complexity, making the system more manageable while enabling high-productivity automated operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11809284B2System and method of cloning a multi-tiered application
Publication Date: 2023.11.07 INFOSYS LTD
  • US11809284B2 patent drawing
  • US11809284B2 patent drawing
  • US11809284B2 patent drawing

AI summary

A method and system of cloning a multi-tiered application is disclosed and it comprises of validating received source server configuration data against received target server configuration data. Further the data at a set of nodes on the target server is restored. The cloning of the multi-tiered application is initiated based on a set of predetermined rules, wherein the cloning comprises a set of sequential actions performed at each of the set of nodes. The method of cloning comprises of generating a set of dynamic configuration files for the set of nodes based on the predefined restore rules and the validation and also generating a set of tokens for the set of nodes to communicate status of refresh. Further the target application is restored based on the set of dynamic configuration files and the set of sequential actions at each of the set of nodes is performed based on the status of set of tokens.