Dynamic Application Server Isolation via Central List Filtering

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In traditional distributed systems, application servers cannot be isolated from processing requests without being visible to the system, which hinders testing and maintenance, introduces errors, and risks data loss due to abrupt shutdowns.

Innovation Solution

Implementing a mechanism where application servers can exist within the system context while being unavailable for processing requests, using central servers to generate lists of active and inactive servers, allowing selective activation and deactivation, and enabling access for administrative tasks like testing and maintenance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If an application server is disabled from receiving external requests but remains visible to the system, then the server can be tested and maintained, but the system may still send requests to the server causing testing errors and data loss

Engineering Contradiction:

Improvetesting reliabilityVSAvoidsystem requests to disabled server

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the visibility of the application server from the system context by removing it from the system's server lists. When a server is disabled, it is taken out of the system's knowledge base, preventing the system from sending requests to it while allowing the server to remain running for testing and maintenance purposes.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary mechanism (the server list maintained by the system) that controls which servers are visible and accessible. By managing server visibility through this intermediary list, the system can prevent requests to disabled servers while maintaining the ability to reactivate them when needed.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If an application server is completely removed from the system context, then no requests are sent to it, but the server cannot be easily reactivated and system knowledge of the server is lost

Engineering Contradiction:

Improverequests to disabled serverVSAvoidserver reactivation capability

Core Design Contradiction:

Object-affected harmful factorsVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by maintaining disabled servers in a suspended state rather than removing them completely. The servers remain in the system's server list with a disabled status, preserving their identity and configuration for future reactivation without requiring full system reinitialization.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements discarding and recovering by temporarily removing disabled servers from the active system context (discarding their visibility) while preserving their existence in the server list. When reactivation is needed, the servers are recovered by restoring their visibility to the system, avoiding complete loss and reinitialization.

Inventive Principle:

Principle #34Discarding and recovering

3Productivity

If an application server remains active in the system, then it can service requests, but testing and maintenance become ineffective and time-consuming

Engineering Contradiction:

Improvetesting efficiencyVSAvoidsystem requests during testing

Core Design Contradiction:

ProductivityVSObject-generated harmful factors

Solution Approach 1:

The patent extracts the application server from the system's active server list during testing and maintenance periods. This removal prevents the system from routing requests to the server under test, isolating the testing environment and eliminating interference from production traffic.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements periodic action by dynamically adding and removing servers from the system context based on their operational state. Servers are periodically included when active and excluded when disabled, creating a rhythmic pattern of visibility that aligns with testing and maintenance cycles.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS8051152B2Isolated application server

Publication Date: 2011.11.01 SAP SE

AI summary

Dynamically isolating application servers, wherein only active application servers are indicated to client applications to prevent access to inactive application servers by the client applications. A central server of a distributed system determines a state of application servers in a system, and generates a list of application servers that includes all application servers of the system including an indication of the state of the application servers. The central server also generates a filtered list of application servers that excludes inactive application servers or application servers in an inactive mode. The filtered list is passed to client applications, which enables the client applications to only access the active application servers, but not access the inactive application servers.