Protocol-Independent Resource Controller for RESTful RFC Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrated development environments (IDEs) and other applications are not fully compatible with Hypertext Transfer Protocol (HTTP), limiting the accessibility of RESTful services, which are typically supported by cloud service providers but not by all systems like IDEs.
Innovation Solution
A protocol-independent resource controller in a business application backend system processes both Remote Function Call (RFC) and HTTP format service requests, enabling RESTful service fulfillment and integration with ABAP backend systems, allowing for HTTP and SAP-proprietary RFC protocol usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If HTTP protocol is used for RESTful services, then accessibility and standard compatibility are improved, but compatibility with IDEs and proprietary systems deteriorates
Solution Approach 1:
The patent introduces a protocol converter as an intermediary component that translates between HTTP and RFC protocols. This mediator enables IDEs to access RESTful services through RFC protocol while maintaining HTTP compatibility for other systems, thus resolving the contradiction between protocol versatility and IDE compatibility
Solution Approach 2:
The patent implements a universal resource controller that can handle both HTTP and RFC protocol requests through a single interface. This multi-functional design allows the system to serve both web-based and IDE-based clients without requiring separate implementations, thereby improving both accessibility and compatibility
2Reliability
If RFC protocol is used for IDE integration, then IDE compatibility is improved, but accessibility for cloud services and web applications deteriorates
Solution Approach 1:
The protocol converter acts as a bidirectional intermediary that translates RFC requests from IDEs into HTTP requests that cloud services can process. This enables IDE integration while maintaining accessibility for web-based cloud services, resolving the contradiction between IDE compatibility and protocol versatility
Solution Approach 2:
The resource controller is designed with universal functionality to accept both RFC and HTTP protocols through a unified interface. This multi-protocol capability ensures that the system remains accessible to both IDE-based and web-based clients, eliminating the trade-off between compatibility and accessibility
3Reliability
If protocol-specific implementations are used, then system compatibility is improved, but integration complexity and development time deteriorates
Solution Approach 1:
The protocol converter serves as a pre-built intermediary layer that handles protocol translation automatically. This eliminates the need for custom protocol implementation in integration projects, reducing development time while maintaining system compatibility through standardized conversion mechanisms
Solution Approach 2:
The universal resource controller provides a single integrated interface that handles both RFC and HTTP protocols. This eliminates the need for separate protocol-specific implementations and reduces integration complexity by consolidating protocol handling into one unified system, thereby reducing development time
Data Source
AI summary
A business application backend system, such as an Advanced Business Application Programming backend can receive and respond to representational state transfer (RESTful) service requests via both HTTP and Remote Function Call (RFC) protocols. In particular, the backend system extracts the RESTful service requests and fulfills the extracted requests using a protocol-independent resource controller. Related apparatus, systems, techniques and articles are also described.