Open Data Protocol (OData) is an information access convention at first characterized by Microsoft. Forms 1.0, 2.0, and 3.0 are delivered under the Microsoft Open Particular Commitment. Form 4.0 is being normalized at OASIS,[1] and was delivered in Spring 2014.[2]
The convention was intended to give standard Muck admittance to an information source through a site. It is like JDBC and ODBC despite the fact that OData isn’t restricted to SQL information bases.
What is OData?
OData stands as a key protocol for building and consuming RESTful APIs. In SAP, it serves as a bridge, enabling seamless communication between different systems and applications.
Key Advantages of OData
- Interoperability: OData acts as a universal language, promoting seamless interoperability across diverse systems and platforms.
- Simplicity in Data Access: Through a RESTful API model, OData simplifies data access, ensuring a streamlined and user-friendly experience.
Open Data Protocol Architecture
OData is based on the AtomPub convention and JSON where the Particle structure is the envelope that contains the information got back from each Open Data Protocol . An OData demand utilizes theREST model for all solicitations. Each REST order is a POST, GET, PUT, Fix, or Erase http demand (planning to Muck) where the particulars of the order are in the url.
- GET: Get an assortment of elements (as a feed report) or a solitary entity(as a section record).
- POST: Make another element from a passage record.
- PUT: Update a current element with a passage record.
- PATCH: Update a current element with an incomplete section record.
- DELETE: Eliminate an element.
Any stage that offers help for HTTP and XML is sufficient to frame HTTP solicitations to associate with AtomPub. The OData particular characterizes how AtomPub is utilized to normalize a composed, asset situated Muck interface for controlling information sources.
Typical Workflow When Creating a New User Interface:-
For all program based application information needs to summon from secure
Service Builder – Data Model:-
Create / Model OData
Artifacts —
- Entity Types
- Entity Sets
- Complex Types
- Associations
- Association Sets
- Function Imports
Can make relationship on guideline to subordinate element with the key field (ex : cardinality 0 :M keep up with )
–
Generation of runtime objects :-
After age of odata antiques it will make 4 class (1 model supplier class and 2 information supplier class) and 2 assistance (specialized model and administration name) .
Service implementation – CRUD methods:-
Direct route into the CRUD –
Methods–
- Create
- Read and Query
- Update
- Delete
On assistance execution Node you can carry out your business rationale . (Open Data Protocol)
Service Builder – runtime artifacts:-
ABAP classes for
- Model definition
- Service implementation
Service registration in the backend
Administration enlistment in the backend. You really want to keep up with framework moniker In exchange SPRO open theSAP Reference IMG and explore to Drain NetWeaver Entryway Administration Enablement – Backend OData Channel – Administration Advancement for Backend OData Channel-Keep up with Models and Keep up with Administrations.
/iwfnd/maint_service :-
Can call your administration straightforwardly on program and furthermore on passage client
Administration archive in the program and element types in
SEGW
There are 5 strategy you can use according to your business rationale and execute .
As you see in underneath result relationship on ID . for more data on Odata joins
you can open your administration on program
http://<host>:<port>/sap/opu/odata/sap/<Service Name >
Synopsis – Exchanges you ought to be aware as an developer:-
| Gateway Node Activation | SICF | Incorporates different capabilities for checking, examination, and investigating in the ICF climate. You can likewise utilize the focal Application Server examination capabilities to recognize issues like execution issues in ICF applications. |
| Gateway Client | /IWFND/GW_CLIENT | SAP NetWeaver Gateway is an amazing asset that improves the current Mistake Log. Likewise permits you to mimic assistance execution. (Like instruments like RESTClient for Firefox) |
| Error Log | /IWFND/ERROR_LOG | The Blunder Log for SAP NetWeaver Gateway center frameworks is a useful expansion to the current Application Log Watcher and gives itemized setting data about mistakes that have happened at runtime. |
| Gateway Service Builder | SEGW | A totally new plan time exchange, which gives engineers a simple to-utilize set of devices for making administrations. It has been imagined for the code-based OData Channel and supports engineers all through the whole improvement life pattern of a help. |
| Register/Test Backend System | SM59 | Your backend framework must be enrolled as a SAP framework nom de plume in the SAP NetWeaver Door Execution Guide (IMG) on your SAP NetWeaver Entryway framework. Moreover, a RFC objective must be characterized in exchange SM59. |
Gateway Service Builder – development flow in detail
this picture reference : CD204 show Teched @ 2012
You may be interested in: