Web Service Gateway for Host Application SOA Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing host applications face difficulties in accessing and integrating Service-Oriented Architecture (SOA) web services due to architectural mismatches, security complexities, and the need for specialized skills, leading to inefficiencies and potential failures in incorporating SOA functionality.

Innovation Solution

A web service gateway provides a single API across all host execution environments, managing target service addresses and security credentials outside the application source, using a transaction server to facilitate seamless communication and error handling, thereby simplifying the integration of SOA web services without requiring extensive training or network topology knowledge.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If host applications directly access SOA web services using standard protocols, then network communication capability is improved, but device complexity and difficulty of operation increase due to requirements for native sockets programming, string manipulation, and XML parsing

Engineering Contradiction:
Improvenetwork communication capabilityVSAvoidprogramming complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a gateway application as an intermediary between host applications and SOA web services. The gateway handles all complex network communication, protocol parsing, and data transformation, while host applications can access web services through simple, standardized API calls. This mediator pattern resolves the contradiction by shielding host applications from complexity while maintaining full network communication capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway application provides a universal interface that works across all host application types and execution environments. By implementing a single, standardized API that the gateway can translate into multiple web service protocols, the system achieves broad adaptability without requiring each host application to implement complex networking logic, thus reducing programming complexity while maintaining versatility.

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

2Adaptability or versatility

If host applications directly access SOA web services, then access capability is improved, but reliability decreases due to lack of centralized error handling and transaction management

Engineering Contradiction:
Improveservice access capabilityVSAvoiderror handling capability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The gateway acts as a centralized intermediary that implements robust error handling, transaction management, and security credentials verification. All web service access goes through the gateway, which can centrally manage errors, implement retry logic, and ensure transaction integrity. This maintains service access capability while significantly improving reliability through centralized control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway implements error handling and transaction management in advance, before host applications need to process web service responses. By pre-configuring error handling strategies, security credentials, and transaction boundaries at the gateway level, the system cushions host applications from potential failures and ensures reliable operation without requiring complex error handling code in each application.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

3Reliability

If security credentials are embedded in host application source code, then authentication capability is improved, but adaptability decreases due to inability to manage credentials outside application source

Engineering Contradiction:
Improveauthentication capabilityVSAvoidcredential management flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent extracts security credentials from host application source code and centralizes them in the gateway application. The gateway stores and manages security credentials externally, allowing them to be updated, rotated, and managed without modifying application code. This extraction maintains authentication capability while dramatically improving adaptability and flexibility in credential management.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The gateway serves as an intermediary that handles all security credential management between host applications and web services. Applications authenticate through the gateway, which manages credentials centrally. This allows the system to maintain strong authentication capabilities while providing flexible credential management through the gateway's external configuration and update mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If multiple target service instances are supported across multiple environments, then adaptability is improved, but device complexity increases due to need to route requests to correct service instances

Engineering Contradiction:
Improvemulti-environment supportVSAvoidservice routing complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The gateway acts as a centralized mediator that manages routing to multiple target service instances across different environments. The gateway maintains knowledge of service endpoints, environments, and routing logic, while host applications simply specify their intended target service. The gateway handles the complexity of routing requests to the correct instance, supporting multi-environment deployment without increasing application complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway provides a universal routing mechanism that works across all host applications and supports multiple target service instances. By implementing a single routing layer at the gateway that can handle multiple environments, service instances, and routing scenarios, the system achieves high adaptability while keeping device complexity concentrated in the gateway rather than distributed across numerous applications.

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

Data Source

PatentUS10244067B1Web service gateway
Publication Date: 2019.03.26 STATE FARM MUTAL AUTOMOBILE INSURANCE COMPANY
  • US10244067B1 patent drawing
  • US10244067B1 patent drawing
  • US10244067B1 patent drawing

AI summary

A web service gateway system includes a host application execution environment including one or more processors, a memory, and a gateway interface configured to receive a gateway copybook input from a host application. The gateway copybook includes input data including a pointer identifying a memory location of a request structure copybook, and output data including a pointer identifying a memory location of a response structure copybook. A gateway program receives the gateway copybook from the gateway interface and invokes a proxy web service with a request using the request structure copybook. The proxy web service maps data from the request structure copybook to web protocol format data, and invokes a target web service with the web protocol format data. The gateway program returns to the gateway interface a response that is based upon a response the gateway program receives from the proxy web service and uses the response structure copybook.