Integration Layer for JavaScript to XML Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Older management systems in enterprises are often slow and outdated, making upgrades time-consuming and resource-intensive, and conventional business planning modules struggle to meet the dynamic needs of different businesses due to static drivers and varying accounting methods.

Innovation Solution

Implementing a system integration that enables communication between a JavaScript-based UI development framework and a Java-based application development framework, using an integration layer to convert process information from JavaScript to XML format for server communication, allowing for dynamic adaptation of business planning models and incremental updates to meet specific enterprise needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If older generation management systems are used, then system stability is maintained, but system performance becomes slow and outdated

Engineering Contradiction:
Improvesystem performanceVSAvoidsystem stability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The system is divided into distinct layers: a modern JavaScript-based UI framework layer for responsive user interaction, an integration layer for communication coordination, and a Java-based ADF layer for backend processing. This segmentation allows each layer to be optimized independently, enabling fast modern UI performance while maintaining stable legacy backend operations.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An integration layer acts as an intermediary between the JavaScript UI framework and the Java ADF framework. This mediator converts process information between JavaScript format and XML format, enabling seamless communication between the modern frontend and legacy backend systems, thus improving overall system performance without compromising stability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If management systems are upgraded to newer versions, then system performance and capabilities are improved, but upgrade time and resource consumption increase

Engineering Contradiction:
Improvesystem performanceVSAvoidupgrade time
Core Design Contradiction:
SpeedVSLoss of time

Solution Approach 1:

The system employs dynamic adaptability where the JavaScript UI framework can independently evolve and update without requiring full system upgrades. The integration layer dynamically handles format conversions and communication protocols, allowing incremental modernization of the UI layer while maintaining compatibility with existing Java ADF backend components, thus reducing upgrade time and resource consumption.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If static business planning modules are used, then system simplicity is maintained, but adaptability to different business needs is reduced

Engineering Contradiction:
Improvebusiness model adaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The JavaScript UI framework provides universal, framework-agnostic process information that can adapt to various business planning scenarios. The integration layer universally handles conversion between JavaScript and XML formats, enabling the system to serve multiple business needs without requiring complex customizations for each specific business case, thus improving adaptability while controlling complexity.

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

Data Source

PatentUS10324692B2Integration for next-generation applications
Publication Date: 2019.06.18 ORACLE INT CORP
  • US10324692B2 patent drawing
  • US10324692B2 patent drawing
  • US10324692B2 patent drawing

AI summary

Implementations generally relate to system integration. In some implementations, a method includes receiving, at an integration layer of a client device, process information from a JavaScript-based user interface (UI) development framework on the client device, where the process information includes command information and event information that is structured in a JavaScript format, where the process information enables one or more webpages to be rendered in a browser, and where the UI development framework is managed by a Java-based application development framework (ADF) on the client device. The method further includes determining a predetermined communication phase of the ADF, where the ADF communicates with a server during the predetermined communication phase. The method further includes sending the process information to the ADF based on the predetermined communication phase of the ADF, where the ADF converts the process information from the JavaScript format into an extensible markup language (XML) format and sends the process information in the XML format to the server.