Parameter, which can be added to the URI: Parameter ($/&) The following tables show some of the parameters and options when consuming an OData service. It became famous as the data source for SAP Fiori Elements and UI5, but is – by no means – limited to that. OData can be used to access SAP backend-systems from various kinds of frontends. If you want to know about the history of OData see: Monday Morning thoughts odata by DJ Adams #Online app builder odata feed registration#Parts 4 to 10 walks you through a creation of an OData service and the registration of the service (as seen here in this blog post in chapter “(1) Creating an OData service using “classical” ABAP”). Part 1 to 3 discusses the general topics about HTTP, REST and OData. The specification of V2 and V4 can be found here:įor more information on OData see the blog post from Anubhav Pandey – “OData – Everything that you need to know (Part 1)”. To read more about the differences, see: “Is it time to switch to OData v4? | SAP Blogs” and “What’s New With OData 4: OData 2 vs. There are different versions of OData, the most common ones, currently used in the SAP-area are V2 and V4. See chapter “Cheat Sheet” for more details. For test purpose the public service of can be used: The public endpoint URI for the OData service. Let’s look at the different parts of the URI in detail: Part OData – the Best Way to REST” which uses the OData example service.You can find more examples at “Understand OData in 6 steps Example URI to retrieve alle persons (you can test these using postman):Įxample URI to retrieve a specific person: The OData service is called via an URI, which encodes the requested service (server, service and entity), and additional selections in the parameters. #Online app builder odata feed software#It is, by definition, independent of any programing language, platform or software product. This way loosely coupled client-server architectures are being made possible. The payload is encoded using JSON or the Atom Syndication Format. Long story short: OData is an open standard, based on REST (Representational State Transfer) and therefore uses the CRUD operators as HTTP-requests (GET, POST, PUT, DELETE) to facilitate machine-to-machine communication. What this definition states, actually is: With OData you can request, exchange and modify data by using URIs via the HTTP protocol… Oh wait, but what’s with APIs, REST and SOAP? (See here for an comprehensive explanation of the differences: Difference between SOAP, REST, ODATA and HTTP protocols – ABusiness Tech and REST oder SOAP? ()). Some of them can help you interact with OData even without knowing anything about the protocol.” (Source: Understand OData in 6 steps (…) The OData metadata, a machine-readable description of the data model of the APIs, enables the creation of powerful generic client proxies and tools. “OData (Open Data Protocol) is an OASIS standard that defines the best practice for building and consuming RESTful APIs. The structure of this blog-post is as follows: Aim is to get an overview of OData and how it can be utilized in the SAP ecosystem. There is SEGW, there is RAP and CAP… I’m aware of the fact that various documents/blogs have been published on the topic of OData already, but for sake of completeness and staying comprehensive, I will touch parts here which you might already know. However, there is more than only this one programing mode. I recently got in touch with OData in connection with the ABAP Programing Model for SAP Fiori.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |