Mainframe Web Service Accelerator Using Visual Builder

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for building and modifying web-based applications in mainframe-based computing environments are complex, requiring multiple skilled personnel and resources, and transitioning from mainframe to distributed architectures complicates data communication and security, impacting efficiency and processing speed.

Innovation Solution

The development of systems and processes that allow users to build and modify screens and applications using configurable parameters rather than traditional programming code, leveraging a mainframe-based platform for enhanced data communication and processing, with an Enterprise Application Integration (EAI) framework facilitating communication between disparate systems and protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If traditional programming approaches are used to build web-based applications, then application functionality can be achieved, but the complexity of the system increases and requires multiple skilled personnel

Engineering Contradiction:
Improveapplication development easeVSAvoidsystem complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent implements a visual application builder that enables end-users to create web-based applications without requiring programming expertise. Users can drag and drop components, configure parameters, and assemble applications through intuitive graphical interfaces, eliminating the need for skilled programmers while maintaining application functionality.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces traditional mechanical programming processes with an automated visual builder system. Instead of writing and compiling code, users interact with graphical components and configuration parameters, substituting the mechanical coding process with a user-friendly visual assembly mechanism that reduces system complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If multiple skilled personnel are engaged for application development, then application quality can be maintained, but time and resources are consumed

Engineering Contradiction:
Improveapplication qualityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The visual application builder enables end-users to independently create and configure applications without requiring assistance from skilled developers. Users can autonomously assemble applications by configuring parameters and arranging components, significantly reducing the time and resources needed while maintaining application quality through built-in validation and templates.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system provides pre-defined templates, component libraries, and configuration parameters that are prepared in advance. Users can select from pre-built components and configure them according to their needs, eliminating the need for developers to create everything from scratch and thereby reducing development time while ensuring quality through standardized components.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If data is pushed to distributed application servers from mainframe, then client access is enabled, but data synchronization complexity increases

Engineering Contradiction:
Improveclient access capabilityVSAvoiddata synchronization complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary data synchronization layer that automatically handles data exchange between mainframe systems and distributed application servers. This intermediary mechanism manages the complexity of data pushing and synchronization automatically, enabling client access without requiring manual intervention or complex synchronization processes.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system replaces manual data synchronization processes with automated mechanisms that handle data exchange between mainframe and distributed servers. The automated data push and synchronization processes eliminate the need for complex manual coordination, simplifying the overall system architecture while maintaining client access capability.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Speed

If applications are copied from mainframe to distributed servers, then processing speed may improve, but security and control are negatively impacted

Engineering Contradiction:
Improveprocessing speedVSAvoidsecurity and control
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements an intermediary layer that maintains secure communication between mainframe systems and distributed servers. This intermediary mechanism ensures that data and applications are transmitted and executed with maintained security protocols and control mechanisms, allowing processing speed improvements without compromising security or control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables distributed servers to perform multiple functions including execution, data processing, and client interface while maintaining secure connections to the mainframe. The universal architecture allows processing speed benefits from distribution while security and control are maintained through standardized secure communication protocols across all server functions.

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

Data Source

PatentUS8510707B1Mainframe-based web service development accelerator
Publication Date: 2013.08.13 PNC FINANCIAL SERVICES GROUP INC
  • US8510707B1 patent drawing
  • US8510707B1 patent drawing
  • US8510707B1 patent drawing

AI summary

An interactive computer architecture is provided that can be employed as a bridge between a mainframe-based computing environment and a distributed server-based computing environment. A request/reply contract can be expressed within the mainframe-based environment and employed as the basis for generating a web service in the distributed computing environment.