Generic OData Mashup Service Framework for Cloud Data Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mashup implementations in mobile device web development are non-generic, requiring specific interfaces and maintenance, leading to high total cost of ownership and limited reuse.
Innovation Solution
The provision of cloud-based, generic Open Data Protocol (OData) mashup services that allow for the instantiation of subservices, data retrieval, and service composition, enabling the reuse of existing services through configuration without reimplementation of business logic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-generic mashup implementations are used, then specific interfaces and functionality are achieved, but total cost of ownership increases and reuse capability decreases
Solution Approach 1:
The patent implements a generic mashup service framework that can handle multiple different data sources and service types through a unified interface. The service definition XML structure allows configuration of various subservices (ERP, web services, databases) without requiring separate implementation for each, enabling one system to perform multiple functions across different business scenarios.
Solution Approach 2:
The mashup service is divided into independent subservices that can be individually configured, instantiated, and managed. Each subservice represents a separate data source or functionality (e.g., ERP system, web service, database) that can be combined in different configurations to create various mashup services, reducing overall system complexity through modular design.
2Ease of operation
If non-generic mashup implementations are designed, then specific intended purposes are achieved, but interface implementation and maintenance effort increases
Solution Approach 1:
A universal service definition format (XML) is implemented that can describe any mashup service configuration, including different subservices, associations, and query operations. This single interface approach allows the system to handle diverse purposes (inventory management, order processing, customer service) without requiring separate interface implementations for each.
Solution Approach 2:
The patent introduces a generic mashup service framework as an intermediary layer between specific data sources and the application layer. This framework provides standardized interfaces for service definition, instantiation, and execution, while the actual data source-specific implementations are encapsulated within subservices, reducing interface implementation effort at the application level.
3Productivity
If multiple separate service implementations are created for different purposes, then specific functionality is achieved, but development time and cost increases
Solution Approach 1:
Multiple service implementations are merged into a single generic mashup service framework that can instantiate different subservices based on configuration. Instead of creating separate deployed services for each business purpose, the system combines them into one framework that dynamically creates and manages subservice instances based on service definition XML files, reducing the number of implementations from many to one.
Solution Approach 2:
Service configurations are prepared in advance using XML definition files that describe the subservices, associations, and query operations needed for different mashup services. This preliminary configuration approach allows services to be instantiated and deployed quickly without requiring separate development and implementation efforts for each service, improving development efficiency.
Data Source
AI summary
The present disclosure describes methods, systems, and computer program products for providing cloud-based, generic OData mashup services. One computer-implemented method includes parsing a received a request for service-related data to determine a subject mashup service associated with the request, retrieving a subject mashup service definition from a service repository, retrieving subservice definitions associated with the subject mashup service definition, instantiating subservices with a computer using the subservice definitions, and transmitting a request to retrieve the service-related data from the instantiated subservices.