Architecture Overview
SAP OData implementation consists of multiple components.
SAP ODATA Components
The various OData components that interact with each other as indicated by Figure 1.
Figure 1: OData components
Table 1 is a list of SAP OData components and their functions.
Components |
Function |
|---|---|
ODP (With Extractors) |
ODP stands for Operational Data Provisioning. It's a framework that allows you to extract and replicate data from various SAP Data Sources (called Extractors). It has the ability to fetch full and delta information. |
CDS Views /Table |
CDS views can be exposed as database views, which means they can be used by external reporting tools or applications that connect directly to the database. |
Reports |
Reports refer to programs that generate formatted output based on data from various sources, typically for the purpose of providing information or facilitating decision-making. ABAP reports are commonly used in SAP systems to display data in a structured and readable format. |
OData Runtime |
Runs instances of MPC (Model Provider Class) and DPC (Data Provider Class) that provide meta data information, acquire data and perform requested operations on the data. |
OData Service |
Receives and interprets incoming OData requests |
Service Builder |
OData service modeler. |
Gateway Client |
Test tool for OData services. |
Up to SAP NetWeaver release 7.31 the OData and SAP Gateway functionalities are delivered with SAP software components IW_FND, GW_CORE and IW_BEP. Starting with SAP NetWeaver release 7.40 all functions are implemented in component SAP_GWFND, which is an integral part of the SAP NetWeaver.
SAP Gateway Deployment Options
Depending on where the individual OData components run, there are multiple options for deploying OData services.
Scenario A: Central Hub
A single instance of SAP Gateway System can link with numerous backend SAP systems. This arrangement not only enhances security but also optimizes performance as both data and the OData Runtime are located on the same system
Scenario B: Central Hub with Deployment in SAP Gateway System
A central instance of the OData Runtime operates on the exclusive central SAP Gateway System, which establishes connections to various backend SAP systems. The SAP Gateway System can be positioned within a demilitarized zone (DMZ), offering enhanced security and reduced maintenance expenses.
Scenario C: Embedded Deployment
Every component is implemented into the backend SAP system. This approach offers the lowest Total Cost of Owner- ship (TCO) as there's no need for a dedicated gateway system. However, this might come with potential constraints in terms of security and scalability.
Secure Gateway Agent
To set up a communication link between the JustPerform Cloud and the SAP system positioned in the client's premises, it's crucial to implement a secure connection. The deployment of the Secure Gateway agent is required to create a VPN (Virtual Private Network), as depicted in Figure 2. If the SAP system is hosted on the cloud, a Gateway service available with a cloud provider can be used instead of a secure gateway agent. It can be configured to allow incoming requests from the JustPerform cloud.
Figure 2: JustPerform Secure Gateway Client
Setting up the Secure Gateway Agent is outside the scope of this document.