File Migration Range Determination via Dependency Graph Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Migrating an existing software stack to cloud or consolidated servers is complex due to diverse software configurations and lack of documentation, making it difficult to identify necessary files for migration, with existing methods being error-prone or product-specific and unable to handle unknown products or ad-hoc configurations.

Innovation Solution

A method and apparatus that compare the source system environment to incremental target environments to discover change files, classify them into change patterns, and determine the range of files to be migrated, reducing the need for human knowledge and specific product expertise.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If automation approach on known products is used (e.g., RAF, UCM, TADDM), then extraction of configurations for specific products is improved, but inability to process unknown products, native components or ad-hoc configurations occurs

Engineering Contradiction:
Improveautomation of configuration extractionVSAvoidability to handle unknown products and ad-hoc configurations
Core Design Contradiction:
Extent of automationVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal configuration extraction framework that can handle multiple types of configurations (standard, ad-hoc, hard-wired) and various software products through a single unified approach. The system uses a generic dependency graph model and pattern matching mechanisms that work across different product types without requiring product-specific tools, thus achieving both automation and versatility simultaneously.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system automatically discovers and extracts configurations by analyzing dependency graphs and identifying patterns in configuration files, without requiring manual intervention or pre-defined product knowledge. The extraction process serves itself by automatically detecting configuration types and extracting relevant information based on observed patterns, enabling it to handle unknown products and ad-hoc configurations that would traditionally require manual analysis.

Inventive Principle:
Principle #25Self-service

2Reliability

If questionnaire method is used, then human knowledge of source environment can be leveraged, but error-prone results occur due to reliance on manual input

Engineering Contradiction:
Improveaccuracy of configuration identificationVSAvoidmanual intervention requirement
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The patent replaces manual questionnaire-based configuration extraction with an automated computational system. Instead of relying on human operators to fill out forms and provide information, the system automatically analyzes dependency graphs, identifies configuration patterns, and extracts configuration information through programmed algorithms, thereby eliminating human error while maintaining high accuracy.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system continuously validates extracted configurations by cross-referencing them against the dependency graph and observed file patterns. When inconsistencies are detected, the system can request clarification or automatically adjust its extraction, creating a feedback loop that ensures high reliability without requiring manual verification of each configuration item.

Inventive Principle:
Principle #23Feedback

3Ease of operation

If manual configuration extraction is performed, then flexibility in handling diverse configurations is maintained, but time-consuming and labor-intensive process occurs

Engineering Contradiction:
Improveflexibility in configuration handlingVSAvoidmigration preparation time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary automated extraction of configuration information by analyzing dependency graphs and identifying patterns before the actual migration process. This preliminary action includes automatically discovering configuration files, extracting their contents, and organizing them into the dependency graph structure, thereby preparing all necessary information in advance and eliminating time-consuming manual analysis during migration.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates a virtual copy of the configuration structure by building a dependency graph that mirrors the actual software environment. This virtual model allows the system to work with simplified representations of configurations rather than manually processing each actual configuration file, significantly reducing time while maintaining the flexibility to handle diverse configuration types through the abstracted graph structure.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9892122B2Method and apparatus for determining a range of files to be migrated
Publication Date: 2018.02.13 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9892122B2 patent drawing
  • US9892122B2 patent drawing
  • US9892122B2 patent drawing

AI summary

A method for determining a range of files to be migrated is disclosed, comprising: comparing the source system environment to be migrated with a set of incremental target system environments, to discover the change files in each of the target system environments relative to the source system environment, wherein each target system environment in the set of incremental target system environments comprises software on which the migration target application depends, and the software contained in the different target system environments is incremental; classifying the change files into different change patterns according to the change types of the change files in each comparison and the different change types of the change files among multiple comparisons; and determining a range of files to be migrated according to the change pattern.