Generic Interface Backend Service Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing backend solutions for business suite systems lack flexibility and adaptability when accessed through diverse computing platforms, such as mobile devices, requiring extensive development efforts and frequent updates to accommodate different business objects and models.
Innovation Solution
A computer-implemented method and system that uses a generic interface and configuration table to identify and adapt business object-related requests, employing a generic metadata provider class and data provider class to access the business logic layer, thereby reducing the need for service-specific implementations and enabling low-cost, efficient access to multiple business objects through OData protocol.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a generic interface with configuration table is used to access business objects, then adaptability to different computing platforms is improved, but service-specific implementation flexibility deteriorates
Solution Approach 1:
The patent implements a universal backend service architecture that can serve multiple computing platforms (mobile devices, tablet computers, smart phones) through a single generic interface. The configuration table stores platform-specific access information, allowing the same service infrastructure to adapt to different platforms without requiring separate service implementations for each device type.
Solution Approach 2:
The system changes parameters by storing platform-specific configuration data (access information, business object definitions) in a configuration table rather than hardcoding them. This allows the service to adapt its behavior based on the requesting platform by retrieving appropriate parameters from the configuration table, eliminating the need for service-specific implementations.
2Adaptability or versatility
If extensive service-specific implementations are created for different platforms, then platform-specific functionality is improved, but development costs and effort increase
Solution Approach 1:
The patent creates a universal backend service that can serve multiple platforms through a single interface. Instead of developing separate services for mobile devices, tablet computers, and smart phones, the system uses one service implementation that retrieves platform-specific configuration from a configuration table, dramatically reducing development costs and effort.
Solution Approach 2:
The system uses configuration table entries as templates or copies of access information for different platforms. Rather than implementing services from scratch for each platform, the configuration table provides pre-defined access patterns and business object definitions that can be copied and adapted for different platform requirements.
3Adaptability or versatility
If frequent metadata updates are performed to accommodate new business objects, then system flexibility is improved, but system stability and maintenance burden worsen
Solution Approach 1:
The patent performs preliminary action by pre-defining business object configurations and access information in the configuration table before runtime. When new business objects need to be accessed, their configuration data is already prepared and stored in the configuration table, eliminating the need for frequent runtime metadata updates and maintaining system stability.
Solution Approach 2:
The system achieves flexibility dynamically by retrieving configuration data from the configuration table at runtime based on the requesting platform and business object, rather than requiring static compilation or frequent metadata updates. The configuration table acts as a dynamic lookup source that adapts to different scenarios without affecting system stability.
Data Source
AI summary
The disclosure generally describes computer-implemented methods, software, and systems for allowing model-based backend services adaptations of business objects. One computer-implemented method includes receiving, at a generic interface associated with at least one backend application, a request for data from a particular backend application, identifying a service for execution associated with the received request based at least in part on the received request, identifying a configuration entry associated with the identified service in a configuration table, where the configuration entry defines a set of access-related information associated with at least one business object associated with the backend application, and requesting data from a business logic layer of the backend application based, at least in part, on the access-related information associated with the at least one business object.