Dynamic Server Configuration via Dependency Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Configuring and initializing combinations of computing devices to provide various server functions is complex due to dependencies among applications and resources, with existing solutions lacking provisions to ease these dependencies and requiring corresponding changes across multiple devices during updates.

Innovation Solution

A combination of virtual machine environments, application software, and dynamic configuration software is used to perform tests and generate databases and catalogs that specify execution requisites, allowing for automated determination and tailored configuration of application routines across multiple computing devices, minimizing the need for custom scripts and ensuring correct order of initialization and restart based on dependencies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration and initialization methods are used for server functions, then flexibility and control are maintained, but the complexity of configuration increases and error-prone manual processes are required

Engineering Contradiction:
ImproveConfiguration simplicityVSAvoidSystem configuration complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system performs self-configuration by automatically discovering application routines, identifying their execution requisites, and determining initialization order without manual intervention. The computing devices autonomously generate and execute configuration scripts based on detected dependencies among applications.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system dynamically changes configuration parameters by detecting the actual state of computing devices and application routines, then automatically adjusting initialization sequences and resource allocations based on discovered dependencies and requisites.

Inventive Principle:
Principle #35Parameter changes

2Productivity

If dependencies among applications are not automated, then manual control is possible, but the time and effort required for configuration and initialization increase significantly

Engineering Contradiction:
ImproveConfiguration speedVSAvoidInitialization time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary discovery of application routines and their execution requisites before initialization begins. By pre-identifying dependencies and generating configuration scripts in advance, the system eliminates time-consuming manual analysis and setup during the actual initialization process.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system continuously monitors the initialization process and adjusts execution sequences based on feedback from detected dependencies and requisites. This real-time feedback mechanism ensures optimal initialization ordering and automatically handles any deviations from the planned sequence.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If custom scripts are created for each application routine, then specific requirements are met, but the effort and complexity of creating and maintaining these scripts increase

Engineering Contradiction:
ImproveApplication-specific configurationVSAvoidScript creation effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system extracts the script creation task from manual operations by automatically generating configuration scripts based on discovered application requisites and dependencies. This extraction eliminates the need for manual script writing while preserving application-specific customization through automated script generation.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system creates a universal configuration mechanism that automatically adapts to different application routines and their specific requirements. A single automated system handles diverse application types by dynamically generating appropriate configuration scripts based on detected dependencies and requisites, eliminating the need for separate manual scripting processes.

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

4Stability of the object's composition

If corresponding changes are made across multiple devices during updates, then consistency is maintained, but the complexity and time required for updates increase

Engineering Contradiction:
ImproveSystem consistencyVSAvoidUpdate management complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The system maintains consistency across multiple devices by continuously monitoring configuration states and automatically detecting changes. When updates are applied to one device, the system provides feedback to identify and coordinate corresponding changes in other devices, ensuring synchronized updates without manual intervention.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

Each computing device performs self-configuration and automatically detects when it needs to be updated based on changes in application routines or dependencies. The system autonomously coordinates updates across the network, with devices automatically applying changes and verifying consistency without requiring centralized manual management.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9553761B2Dynamic server to server configuration and initialization
Publication Date: 2017.01.24 SAS INSTITUTE INC
  • US9553761B2 patent drawing
  • US9553761B2 patent drawing
  • US9553761B2 patent drawing

AI summary

An apparatus includes a discovery component to identify a first application routine within a storage for execution, to identify execution of a remote application routine within a node device as a first requisite for execution of the first application routine from a first application requisites data, and to provide indications of storage of the first application routine and the first requisite to a control master; a start component to restart an earlier started execution of the first application routine in response to receipt of an indication that execution of the remote application routine within the node device has been restarted in accordance with a catalog received from the control master, the catalog including indications of the first and remote application routines and an indication of the first requisite; and a status component to provide an indication to the control master of the restart of execution of the first application routine.