Web Module Mediator for Browser-Engine Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies face challenges in integrating Web browsers as Web Service servers within business process engines, as conventional Web browsers cannot be directly invoked or interacted with due to differences in communication protocols and data formats between Web browsers and business process engines.
Innovation Solution
A system and method that utilize a Web module to convert information exchanged between a business process engine and a Web browser, allowing the business process engine to invoke the Web browser as a Web Service server by converting HTTP requests to XML documents and using servlets and predefined page templates to manage the interaction, enabling the Web browser to operate as a quasi-Web Service server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If Web browsers are integrated as Web Service servers within business process engines, then interoperability and integration capabilities are improved, but protocol and data format differences create technical barriers
Solution Approach 1:
The patent introduces a Web module as an intermediary component that sits between the business process engine and the Web browser. This module translates HTTP requests into XML documents that the business process engine can process, and converts browser responses into formats the engine can understand. The intermediary resolves the protocol compatibility issue by acting as a translator between the XML-based business process engine and the HTTP-based Web browser ecosystem.
2Adaptability or versatility
If conventional Web browsers are invoked as Web Service servers, then browser functionality is utilized, but direct invocation is not possible due to protocol differences
Solution Approach 1:
The Web module serves as a mediator that enables the business process engine to invoke the Web browser indirectly. Instead of directly calling browser methods, the engine sends HTTP requests through the Web module, which then renders appropriate Web pages and captures user interactions. This indirect invocation mechanism maintains browser functionality while making it compatible with the business process engine's XML-based architecture.
Solution Approach 2:
The patent replaces direct mechanical invocation of browser methods with an HTTP-based communication mechanism. The business process engine uses standard HTTP requests and responses to interact with the browser, substituting the need for direct programmatic browser access with a more compatible web protocol layer that the Web module manages.
3Adaptability or versatility
If information conversion between business process engine and Web browser is implemented, then seamless interaction is enabled, but conversion complexity increases
Solution Approach 1:
The Web module acts as an intermediary that handles all data conversion between the business process engine and the Web browser. It automatically translates HTTP requests into XML documents for the engine to process, and converts browser responses back into appropriate formats. This centralized conversion approach manages the complexity by consolidating all protocol translation in one module rather than scattering it throughout the system.
Data Source
AI summary
Systems and techniques for using a Web-service based business process to interact with a Web browser as if the Web browser were a Web service server. In one exemplary implementation, an interface module with a HTTP server is provided to convert data from the Web browser into an XML document from a Web service server and to convert data from the business process engine in an XML document to a Web service server into a Web page for the Web browser. The business process engine may be programmed in the Business Process Execution Language for Web Services (BPEL) or other suitable business process execution languages.