API Servlet Automation for Bulk Administrative Tasks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional web-based GUIs limit administrator interaction with underlying software, restricting data input and format, making it difficult to automate routine administrative tasks on multiple computing machines, especially in large networks, leading to increased time and effort for administrators.

Innovation Solution

The enhancement of the API by initializing a servlet on a centralized server, using XML-RPCs and custom serializers to expand capabilities, allowing for bulk automation of administrative tasks without user intervention through the integration with other scripts and programs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a conventional web-based GUI is used to manage software, then the interface is easy to use with user-friendly navigation, but the administrator cannot automate routine administrative tasks and has limited interaction with underlying software

Engineering Contradiction:
Improveease of useVSAvoidautomation capability
Core Design Contradiction:
Ease of operationVSExtent of automation

Solution Approach 1:

The patent introduces an API as an intermediary layer between the web-based GUI and the underlying software. This API enables automated scripts to interact with the software's core functions while the GUI remains unchanged for user-friendly operations. The API acts as a mediator that translates automated requests into actions that the underlying software can execute, thus enabling automation without compromising the ease of use of the GUI interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a conventional web-based GUI is used for administrative tasks, then the interface provides indirect access to software data and functions, but it limits the type and format of data that can be input, preventing direct access to underlying software

Engineering Contradiction:
Improveuser-friendly interfaceVSAvoiddata input flexibility
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments the interaction interface into two distinct parts: the web-based GUI for user-friendly indirect access, and the API for direct access with flexible data input. This segmentation allows each interface to be optimized for its specific purpose - the GUI maintains ease of use while the API provides versatility in data input formats and direct software interaction, eliminating the need for administrators to choose between user-friendliness and flexibility.

Inventive Principle:
Principle #1Segmentation

3Ease of operation

If an administrator manually performs routine administrative tasks on multiple computing machines through the web-based GUI, then the interface remains simple to use, but it takes a long time to complete tasks across large networks

Engineering Contradiction:
Improvesimplicity of interfaceVSAvoidtask completion speed
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The patent merges the capabilities of the simple web-based GUI with the automation power of API-based scripting. By combining these two approaches, administrators can use the GUI for complex one-time tasks while leveraging automated scripts for routine repetitive tasks across multiple machines. This merging allows the system to maintain interface simplicity while dramatically improving productivity through automated bulk operations.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8225337B2Application programming interface enhancement
Publication Date: 2012.07.17 RED HAT INC
  • US8225337B2 patent drawing
  • US8225337B2 patent drawing
  • US8225337B2 patent drawing

AI summary

Some embodiments of application programming interface (API) enhancement in a networked system have been presented. In one embodiment, a servlet is initialized on a centralized server in the networked system. The capabilities of an application programming interface (API) accessible by the client are expanded to allow the client to have data converted to a predetermined format when executing an automation script in order to perform an administrative task on multiple computing machines in the networked system without user intervention.