End-to-End Application Infrastructure Mapping via Tiered Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing IT infrastructure discovery systems fail to accurately and non-disruptively map business applications to their underlying server infrastructure, especially in complex distributed systems with multiple middleware tiers, leading to coarse-grain mappings and intrusive discovery methods.
Innovation Solution
A method and system that determine associations between data instances, data-container configuration elements, and server infrastructure at each distributed system tier, composing end-to-end associations to represent application dependencies on server infrastructure without disrupting the system, using a computer-implemented module to discover and store these associations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If existing IT infrastructure discovery systems are used to map applications to server infrastructure, then discovery can be performed, but the mapping accuracy is coarse-grain and cannot drill through middleware tiers to specific resources
Solution Approach 1:
The patent segments the discovery process into multiple tiers, where each tier discovers associations between adjacent layers (application tier to middleware tier, middleware tier to infrastructure tier). This segmentation allows the system to drill through complex middleware stacks by breaking down the overall discovery task into manageable per-tier components, achieving fine-grain mapping accuracy without overwhelming system complexity.
Solution Approach 2:
The patent introduces an intermediary discovery mechanism that operates at each tier to bridge the gap between adjacent layers. Rather than attempting direct end-to-end discovery through multiple middleware tiers, the system uses intermediate discovery points at each tier to progressively trace associations from application to infrastructure, maintaining accuracy while managing complexity through staged intermediation.
2Measurement precision
If active discovery techniques (e.g., fault injection) are used to obtain finer-grain dependency information, then mapping precision improves, but the IT environment is disrupted
Solution Approach 1:
The patent enables each tier to perform self-discovery of its associations with adjacent tiers using passive observation and configuration data analysis. Rather than requiring external fault injection or active probing that disrupts the system, each tier autonomously discovers its dependencies by analyzing its own configuration and runtime behavior, achieving fine-grain accuracy without compromising system reliability.
Solution Approach 2:
The patent performs discovery actions in advance by analyzing configuration data and establishing associations before any potential failures occur. This preliminary discovery using passive methods eliminates the need for disruptive fault injection techniques, as the dependency map is constructed proactively from available configuration and runtime information without interrupting normal system operation.
3Ease of manufacture
If existing discovery systems assume application depends on total IT infrastructure used to support middleware, then discovery is simpler, but resource alignment accuracy deteriorates
Solution Approach 1:
The patent applies local quality by determining associations at each specific tier rather than applying a blanket assumption across the entire infrastructure. Each tier discovers and records its specific associations with adjacent tiers, creating a localized and accurate view of resource usage at each level. This per-tier local discovery approach replaces the coarse-grain global assumption, achieving precise resource alignment while maintaining manageable discovery processes.
Data Source
AI summary
A methodology is presented for discovering and storing end-to-end associations between different types of entities in a system configuration model of a distributed middleware system. First associations are determined, at each distributed system tier, between instances of data and data-container configuration elements. Those first associations point to logical subdivision of a data service that is directly responsible for implementing an instance of data. Second associations are determined, at said each distributed system tier, between said data-container configuration elements and a server infrastructure. Said second associations point to a server infrastructure that hosts said data-container configuration elements. Third associations are composed, within said each distributed system tier, between said instances of data and said server infrastructure, using said first associations and said second associations. Fourth associations are composed, end-to-end, which represent dependency of an application using said instances of data to said server infrastructure.