Automated Server Domain Configuration via Reusable Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Building out and testing server systems are hindered by security protocols, variance in use cases, and communication issues between remote servers, necessitating a solution that ensures consistent installation aligned with security standards and versatile enough to cover multiple business lines without requiring separate solutions for each use case.

Innovation Solution

A system comprising memory devices with computer-readable program code and processing devices that configure and monitor server virtual machines, manage node managers, and encrypt passwords, ensuring secure and automated domain creation, startup, shutdown, and configuration across multiple servers, while checking for port conflicts and security protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual server system building and testing is performed, then flexibility in handling different use cases is improved, but installation consistency and security compliance deteriorate

Engineering Contradiction:
Improveflexibility in handling different use casesVSAvoidinstallation consistency
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The patent uses templates to define server system configurations, security protocols, and testing procedures. These templates serve as reusable copies that ensure consistent installation outcomes across different use cases while maintaining security compliance and adaptability through parameter customization.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system allows modification of template parameters to adapt to different use cases (e.g., server type, security requirements, business line specifics) while the underlying installation process remains consistent. This enables flexibility through parameter variation without sacrificing installation consistency.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If separate solutions are created for each use case, then adaptability to specific business lines is improved, but system complexity and deployment time worsen

Engineering Contradiction:
Improveadaptability to specific business linesVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal server system template that can serve multiple business lines and use cases. The template incorporates configurable parameters and modular components that can be adapted to different requirements without creating separate solutions, thereby reducing system complexity while maintaining versatility.

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

Solution Approach 2:

The system divides the server configuration into modular, reusable components and templates. Each template represents a segment that can be independently configured and combined to meet specific business line requirements, reducing overall system complexity through modularity.

Inventive Principle:
Principle #1Segmentation

3Manufacturing precision

If automated domain creation and testing is implemented, then installation consistency is improved, but the complexity of automation scripting worsens

Engineering Contradiction:
Improveinstallation consistencyVSAvoidautomation scripting complexity
Core Design Contradiction:
Manufacturing precisionVSDevice complexity

Solution Approach 1:

The patent uses pre-defined templates and scripts that can be copied and reused across multiple domain creations. This eliminates the need to write complex automation scripts from scratch for each installation, achieving installation consistency while keeping the automation approach simple through template reuse.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary configuration and validation through templates before actual domain creation. This pre-prepared automation framework handles complex scripting requirements in advance, simplifying the execution phase while ensuring installation consistency.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If security protocols are strictly enforced during server building, then security compliance is improved, but installation time and process complexity worsen

Engineering Contradiction:
Improvesecurity complianceVSAvoidinstallation time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent incorporates security protocol validation and configuration into the templates during the design phase. This preliminary action ensures security compliance is built-in from the start, eliminating the need for time-consuming security checks and adjustments during actual installation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Security configurations and protocols are defined as reusable template components that can be copied across multiple deployments. This ensures consistent security compliance while reducing installation time through template reuse rather than manual configuration.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10417073B2Application server deployment system for domain generation and testing with an administrative server virtual machine and managed server virtual machines
Publication Date: 2019.09.17 BANK OF AMERICA CORP
  • US10417073B2 patent drawing
  • US10417073B2 patent drawing
  • US10417073B2 patent drawing

AI summary

Embodiments of the present invention provide a system for building out and testing a wide range of server systems configured to meet varied use cases across a large enterprise. The systems described herein provide automated solutions for building out a domain that is specific to a user's use case needs, across multiple product versions, and within a large enterprise environment comprising rigorous security protocols. Generally, the system automates certain domain creation functions, automatically shuts down, starts up, and monitors functions as they occur in the domain to identify any potential errors. Additionally, techniques are described to build out and test adjustments to currently-existing domains in the same manner.