Dynamic Workflow Composite Web Service Definition
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web service systems lack dynamic definition and management of endpoints, methods, and properties, leading to inflexible data exchange between software systems, which complicates data communication and troubleshooting across different programming languages.
Innovation Solution
A dynamic workflow-based composite web service system that utilizes event triggers to define endpoints, actor classes to define properties and metadata, and workflows to dynamically define and manage methods and functions, allowing for multiple endpoints, shared actors, and handling multiple incoming requests by processing each as a separate thread.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web services are defined using static WSDL files and fixed programming languages, then communication rules are clearly defined, but the system lacks flexibility and requires recompilation for modifications
Solution Approach 1:
The patent implements dynamic web service definition by replacing static WSDL files with runtime-configurable service definitions. Services can be created, modified, and deployed without recompilation through dynamic service registration and configuration mechanisms that allow services to be defined and updated during execution.
Solution Approach 2:
The patent segments the monolithic WSDL definition into separate, independently manageable components including service definitions, operation definitions, and data type definitions. This allows individual services and operations to be modified without affecting the entire system, enabling granular updates and reducing management complexity.
2Adaptability or versatility
If multiple software systems use different programming languages, then system diversity is supported, but data exchange becomes complicated
Solution Approach 1:
The patent introduces a universal service definition framework that acts as an intermediary between different programming languages and systems. This framework provides language-agnostic service descriptions and data exchange formats that enable seamless communication between heterogeneous systems without requiring language-specific adaptations.
Solution Approach 2:
The patent creates a universal service interface that can be implemented across multiple programming languages while maintaining consistent behavior and data exchange protocols. The service definitions and data types are designed to be language-independent, allowing the same service to be accessed from different language environments through a unified interface.
3Adaptability or versatility
If web service definitions are modified in traditional systems, then updates are made, but recompilation is required which reduces productivity
Solution Approach 1:
The patent enables dynamic service modification by allowing service definitions to be changed at runtime without requiring system recompilation. Services can be added, removed, or modified through dynamic configuration and registration mechanisms that take effect immediately, dramatically accelerating the deployment cycle.
Solution Approach 2:
The patent implements service templates and pre-defined service patterns that allow common service configurations to be prepared in advance. When services need to be deployed or modified, these pre-prepared templates can be instantiated and customized quickly, reducing the time required for service creation and modification.
Data Source
AI summary
A dynamic workflow-based composite web service system and method for the creation and definition of a web service, its properties, methods, and functions through the combination of an event trigger which defines the web service endpoint, actor classes which defines the service's properties and metadata, and a workflow which defines its methods and functions. The dynamic workflow-based composite web service system and method generally includes one or more web service endpoints (the URL where the service can be accessed by a client application), an event trigger defined for each endpoint, actors which define the properties and metadata of the service, and a workflow which receives input from the endpoint, returns the result of the process, and defines the web service functions and methods.