Composite Application Deployment via Abstract Pattern Binding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Deployment architects face challenges in adapting deployment artifacts and configurations for composite applications across different environments due to lack of knowledge about target deployment resources and requirements, leading to complex and manual processes.

Innovation Solution

A computer-implemented method that uses an abstract pattern lacking resource-related data, which is iteratively supplemented with concrete resource information from a target infrastructure's resource catalog, enabling automated deployment and instantiation of composite applications without requiring detailed knowledge of the target environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If detailed information of the deployment target environment is required for automated deployment, then deployment precision is improved, but deployment complexity increases

Engineering Contradiction:
Improvedeployment precisionVSAvoiddeployment complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent segments the deployment process into two distinct phases: (1) creating an abstract deployment pattern that defines the application structure and resource requirements without environment-specific details, and (2) automatically binding this pattern to concrete target environment resources through iterative evaluation. This segmentation allows deployment architects to work with simplified abstract patterns while the system handles the complexity of environment-specific bindings automatically.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an abstract deployment pattern as an intermediary layer between the application deployment requirements and the target environment resources. This intermediate representation decouples the deployment logic from environment-specific details, allowing automated binding processes to bridge the gap without requiring architects to directly manage complex environment configurations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If deployment architects manually adapt deployment artifacts and configurations, then deployment reliability is improved, but productivity decreases

Engineering Contradiction:
Improvedeployment reliabilityVSAvoiddeployment productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent enables the deployment system to perform self-service by automatically evaluating the abstract deployment pattern against the target environment's resource catalog and iteratively binding appropriate resources. This automated self-binding process eliminates the need for manual adaptation of deployment artifacts while maintaining reliability through systematic evaluation and matching of resource capabilities to application requirements.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary actions by pre-defining the abstract deployment pattern that captures all necessary deployment logic and resource requirements before the actual deployment to the target environment. This preliminary abstraction allows the system to automatically adapt to different target environments without requiring manual reconfiguration, thereby improving both productivity and consistency across deployments.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If abstract pattern lacks resource-related data, then adaptability is improved, but automation capability deteriorates

Engineering Contradiction:
ImproveadaptabilityVSAvoidautomation capability
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The patent transforms the static abstract deployment pattern into a dynamic structure that is iteratively enriched during the binding process. The pattern starts as a resource-agnostic template that ensures adaptability, then dynamically incorporates concrete resource bindings through automated evaluation of the target environment's resource catalog, thereby achieving both adaptability and automation capability.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent replaces the manual mechanical process of adapting deployment configurations with an automated computational system that iteratively evaluates the abstract pattern against the resource catalog and performs bindings. This substitution of manual mechanical adaptation with automated computational evaluation enables the system to maintain adaptability while achieving full automation capability.

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

Data Source

PatentUS11212341B2Deployment management of composite applications
Publication Date: 2021.12.28 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11212341B2 patent drawing
  • US11212341B2 patent drawing
  • US11212341B2 patent drawing

AI summary

A source IT-infrastructure hosts a composite application including multiple functional modules connected to each other via communication links. An abstract pattern includes first nodes and first links representing the functional modules and communication links and lacks resource-related data enabling a deployment engine to instantiate a resource for providing a runtime environment. A target IT-infrastructure has assigned a resource catalog including, for each resource available in the target IT-infrastructure, a specification of the resource's capabilities, and includes second nodes and links, each second node being a representation of one or more of the resources of the target IT-infrastructure and including an indication of the capabilities of one or more resources represented by the second node. The first nodes and links of the abstract pattern are iteratively supplemented by the second nodes and second links.