Application Server Provisioning Template Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for configuring application servers are not scalable, requiring deep knowledge of formatting and syntaxes, leading to time-consuming, costly, and error-prone manual processes for importing and modifying features across different servers.

Innovation Solution

Dynamic generation of provisioning templates that can be quickly ported to other application servers, allowing for introspection to determine available features and configurations, and generating a generic description that can be used to import features without specific implementation details, reducing the need for manual mapping and increasing flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual configuration files are written for each application server, then developers can specify provisioning features, but the process becomes time-consuming, costly, and error-prone due to required deep knowledge of formatting and syntaxes

Engineering Contradiction:
Improveconfiguration accuracyVSAvoidconfiguration time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent uses introspection to automatically generate provisioning configuration files by copying and adapting the structure and content from an existing application server configuration. This eliminates manual writing of configuration files while maintaining accuracy, as the system replicates proven working configurations rather than requiring developers to recreate them from scratch with deep knowledge of syntax and formatting requirements

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The application server performs self-introspection to automatically generate its own provisioning configuration files. The server examines its current state, identifies its features and capabilities, and autonomously produces the configuration documentation without human intervention. This self-service approach eliminates the need for developers to manually document configurations while ensuring accuracy reflects the actual server state

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If developers manually import features from one application server to another, then feature porting is possible, but the process requires deep knowledge of the application server to build the management model correctly

Engineering Contradiction:
Improvefeature portabilityVSAvoidimport operation ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent automatically copies feature definitions and management model structures from the source application server to the target server through introspection-generated configuration files. This copying process preserves the exact feature specifications and relationships without requiring developers to manually reconstruct the management model, thereby maintaining feature portability while dramatically simplifying the import operation

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces introspection-generated provisioning configuration files as an intermediary between source and target application servers. These configuration files serve as a standardized exchange format that automatically translates features from one server to another, eliminating the need for developers to directly manipulate complex management models and reducing the knowledge required for feature porting

Inventive Principle:
Principle #24Intermediary (Mediator)

3Extent of automation

If provisioning templates are dynamically generated through introspection, then feature porting is automated and flexible, but the system must perform runtime analysis to determine available features and configurations

Engineering Contradiction:
Improveprovisioning automationVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The application server performs self-introspection to automatically generate provisioning templates by examining its own runtime state. This self-service approach automates the provisioning template generation process without requiring external tools or complex manual procedures, achieving high automation while managing system complexity through the server's inherent ability to self-describe its features and configurations

Inventive Principle:
Principle #25Self-service

4Manufacturing precision

If manual configuration writing is required for each server, then specific server implementations can be precisely configured, but developers need extensive knowledge of each server's formatting and syntaxes

Engineering Contradiction:
Improveconfiguration precisionVSAvoidconfiguration ease
Core Design Contradiction:
Manufacturing precisionVSEase of operation

Solution Approach 1:

The patent copies configuration structures from existing application server implementations, preserving the precise formatting and syntax requirements of each specific server type. By replicating proven configuration patterns rather than requiring developers to invent them, the system maintains configuration precision for each server implementation while significantly improving ease of operation, as developers work with copied templates rather than writing configurations from scratch

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10958514B2Generating application-server provisioning configurations
Publication Date: 2021.03.23 RED HAT INC
  • US10958514B2 patent drawing
  • US10958514B2 patent drawing
  • US10958514B2 patent drawing

AI summary

Systems, methods, and non-transitory computer-readable media are disclosed for generating provisioning templates for application servers. An example method includes loading a first application server in a runtime environment, identifying features and associated files used by the first application server at runtime, generating a provisioning template including a description of the subset of the identified features and how the files support each of the subset of features, and using the provisioning template to configure a second application server.