In the previous five parts on SAP Netweaver Gateway and OData Tutorials, we performed some hands-on learning with some technical insights. For ABAPers those tutorials would be beneficial and enough but there are some terminologies and jargons we should know so that we can express what we know. And we can participate in the discussions and positive debates. The below commonly asked concepts might help you in understanding the terminologies already demonstrated in earlier parts even better.
Some of you might feel, this post should be the first article in the series. You are right my friend. Everyone put this topic in their introduction part. But at SAPYard, we show the real stuffs (hands-on SAP) first and give you the fundamentals after that we beat around the bush to provide more clarity. 🙂
Who developed OData?
Ans: Microsoft, 2007.
Who were all the main players in standardizing the OData?
Ans: Microsoft, IBM and SAP, along with Citrix, Progressive Software, WSO2.
Does Microsoft manage OData now or some other organization?
Ans: Now OData is managed by the Oasis Organisation (Organization for the Advancement of Structured Information Standards).
What is the benefit of OData?
• OData is lightweight and is built on the HTTP protocol which allows database-like access to data via the web
• Decouples the data provisioning from the UI designer by providing a bridge between SAP developers and UI designer(non-SAP developers)
• It supports multichannel access to SAP data as it is supported by multiple platforms
• The standard address representation or resource is the URI (Uniform Resource Identifier) and all players can easily access it
• XML-based Atom Pub format and the JSON format is popular industry-wide used formats which OData supports. This makes it easy to learn, understand, connect and consume.
• OData messages are self-describing and hence all non-SAP developers are able to understand the content of the OData message without the need to have any knowledge of how SAP ERP system works.
• There is no expense associated with the use of OData. It is open and anyone can use it with no cost or license agreement.
• OData is extensible.
When was SAP Netweaver Gateway Launched?
Ans: May 2011.
What is SAP Netweaver Gateway?
Ans: It is a technology which provides a simple way connect to SAP Software from devices, environments and platforms based on common market/industry standards. In other words, it is a platform which allows connectivity to SAP Applications using any programming language or model without the need of prior SAP knowledge.
As we repeatedly said in all our previous articles, SAP Netweaver Gateway is a way (gate) or window for the outer world to peep into SAP. With the help of SAP Netweaver Gateway, front end developer of non-SAP system can develop applications which can consume data from SAP and that too without any knowledge of SAP.
It would not be wrong if we say SAP Netweaver Gateway is a platform which exposes all the back-end SAP data as OData which can be easily consumed by outside non-SAP world. SAP Netweaver Gateway unifies access to SAP data and processes via OData protocol.
What is the difference between OData and OData Service?
Ans: OData is a web protocol for retrieving and updating data. It is built on commonly known and extensively used industry standards like XML, JSON, which makes it easier to use and understand. While OData Service implements OData protocol and expose endpoints which allow access to SAP Applications and Data.
What is the benefit of SAP Netweaver Gateway?
• SAP Netweaver Gateway makes it possible to provide a single solution to multiple consumers via OData Services. So point to point solution which can be complex and expensive can be avoided and replaced with SAP Netweaver Gateway and OData Service single point solution.
• The frontend can be any device or technology i.e. backend developers (ABAPers) can create OData services without worrying who and what frontend technology would consume them. So, there can be segregation of duties of Frontend and Backend Developers.
• Installation of SAP Netweaver Gateway is simple and Non-Disruptive (zero down time)
• Fulfills all requirements of modern business applications i.e. End User Expectation and Business Application Requirement.
Also Read: End to End Implementation of Fiori App
What is the architecture of SAP Netweaver Gateway?
Ans: Like SAP, SAP Netweaver Gateway’s Architecture also consists of 3 Tiers.
• The SAP Business Suit Tier (Backend)
• The SAP Netweaver Gateway Tier (Heart + Middle Man)
• The Consumer Tier (Frontend)
Tier 1: SAP Business Suit Tier
• Application Data resides here and so also the business logic.
• It consists of Development Tools (Service Builder i.e. T-code SEGW) and Service Provider Implementation based on the Add-on IW_BEP (Business Enablement & Event Provisioning).
• Service Provider Implementation in turn, provides connectivity to SAP Business Suit system and can connect to a variety of SAP Interfaces such as BAPIs, RFCs, BW, HANA, BOL etc.
Tier 2: SAP Netweaver Gateway Tier
• Holds major part of Netweaver Gateway functionalities and Components including core component
• Connecting link between Business Suit Layer and Consumer Layer
• Provides tools for creation and development of services
• Service Registry stores the linkage between the OData Service and the actual implementation of the service
• Consists of Runtime Components, Metadata Components and OData Library
Consists of OData specific runtime that processes OData requests and functionality to expose OData services
Manages metadata that describes OData models that are exposed as OData Service document and OData Service metadata document
Consists of SAP specific metadata that consumes SAP Business data retrieved from SAP Data Dictionary.
Tier 3: Consumer Tier
• Are UI-centric clients viz Web applications, Enterprise software, Desktops, Tablets, Mobile devices.
• Actual consumption of SAP Netweaver Gateway service takes place in Consumer layer
• Can create applications which can easily and quickly consume services
• Two types of components are found in Consumer Layer.
i) SAP Netweaver Gateway Consumer
ii) Integrated Development Environments (IDEs) – Standard environments like Eclipse or MS Visual Studio.
How does SAP Netweaver Application Server communicate with Web Browser?
Ans: Through ICM (Internet Communication Manager).
ICM contains the TCP/IP(Transmission Control Protocol/Internet Protocol) basic function and thus SMTP(Simple Mail Transfer Protocol) communication with SAP Netweaver Application Server is possible.
This is one of the rare articles on SAPYard which is purely theoretical. Although we believe more on hands-on technical knowledge but at times we need to know how to articulate our technical concepts correctly. Hopefully, this article would help us in adding more clarity to our technical know-how.
In the next part of SAP Netweaver Gateway and OData series, we would show you how to consume the SAP OData Service which we create in previous parts and use them in our SAPUI5 Applications. Till then, please get your concepts brushed up and get ready with your SAP system again. Even we (Team SAPYard) like posting images from real SAP system and not from PPTs or PDFs. 🙂
If you GENUINELY like our articles then it would be a HUGE help if you subscribed and liked us on facebook. It might seem insignificant, but it helps more than you might think.
Do you have anything to add to this article? Do you have any other questions and answers? Do you want to share any real project requirement or solutions? Please do not hold back. Please leave your thoughts in the comment section.
Thank you very much for your time!!
Do you have any tips or tricks to share? Do you want to write some articles at SAPYard? Please REGISTER and start posting and sharing your knowledge to the SAP world and get connected to your readers. Please check our simple guidelines for contributing your articles and receiving the gifts.
Step by Step Tutorials on SAP Netweaver Gateway and OData
- OData and SAP Netweaver Gateway. Part I. Introduction
- OData and SAP Netweaver Gateway. Part II. Create your first OData Service
- OData and SAP Netweaver Gateway. Part III. Query Options in OData Service URI
- OData and SAP Netweaver Gateway. Part IV. Association and Navigation in OData Service
- OData and SAP Netweaver Gateway. Part V. CRUD Operations in OData Services
- OData and SAP Netweaver Gateway. Part VI. Frequently Asked Questions
- OData and SAP Netweaver Gateway. Part VII. Debugging, Trace, Cache Cleanup and F4 Help
- OData and SAP Netweaver Gateway. Part VIII. SAP’s Love for OData – a Tale of the Friendly ABAPer
- ABAP on SAP HANA: Part XV. Expose CDS Views as OData Service through Annotation
- OData and SAP Netweaver Gateway. Part IX. How to Add Multiple Entities in One Operation in OData Service
- OData and SAP Netweaver Gateway. Part X. How to Delete OData Service from Service Catalog?
- OData and SAP Netweaver Gateway. Part XI. Query Options & HTTP Status Code Summary
- SAP Netweaver Gateway and OData. Part XII. Media Handling using OData Gateways
- SAP Netweaver Gateway and OData. Part XIII. Entity Tags in SAP OData Gateways
Also, Check Step by Step Tutorials on SAPUI5
- Journey to SAPUI5
- SAPUI5 Tutorial with WebIDE. Part I. How to Consume Custom OData in SAPUI5 Application
- SAPUI5 Tutorial with WebIDE. Part II. Routing and Navigation in SAPUI5 Application
- SAPUI5 Tutorial with WebIDE. Part III. Drop Down in SAPUI5 Applications (2 Methods)
- SAPUI5 Tutorial. Part IV with WebIDE. Routers and Routing in SAPUI5
- SAPUI5 Tutorial with WebIDE. Part V. Navigation in SAPUI5 without Routers
- SAPUI5 Tutorial with WebIDE. Part VI. Using Fragments in SAPUI5 Fiori Applications
- SAPUI5 Tutorial with WebIDE. Part VII. An ABAPer’s First SAPUI5 App in SAP WebIDE
- SAPUI5 Tutorial with WebIDE. Part VIII. Deploy my First SAPUI5 App in WebIDE
- SAPUI5 Tutorial with WebIDE. Part IX. Alternative to oModel.setSizeLimit()
- SAPUI5 Tutorial with WebIDE. Part X. Using Media Queries in UI5 Application
- SAPUI5 Tutorial with WebIDE. Part XI. An ABAPer’s Second SAPUI5 App
- SAPUI5 Tutorial with WebIDE. Part XII. SAPUI5 Basic Debugging for Beginners
- Routing and Navigation in SAP UI5 – Theoretical Explanation Part 1
- Routing and Navigation in SAP UI5 – Theoretical Explanation Part 2
We have a very active Telegram SAP Technical Group. Please join it using below link.
Telegram SAP Technical Discuss Group.
WhatsApp had the limitation of 256 members per group and we were finding a hard time syncing and maintaining information in multiple WhatsApp group. Therefore we have moved to Telegram as it can accommodate more than 10,000 users. Please join.