Completed
Distinguishing between the service document and the metadata document - the two "well known" documents of any OData service
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Exploring API Specifications on the SAP API Business Hub
Automatically move to the next video in the Classroom when playback concludes
- 1 Welcome and introduction with some extra rambling about my setup
- 2 Moving to the SAP API Business Hub
- 3 Starting to dive into the SAP S/4HANA product
- 4 Filtering down to the OData V2 APIs and the Business Partner A2X API
- 5 Exploring what the SAP API Business Hub tells us about this API schema, attrs, spec, extensibility, auth, SAP Cloud SDK support and more
- 6 Looking at some of the API endpoints and noticing the OData system query options, plus the classic OData v2 JSON response format with the 'd' property
- 7 Having our first 'try out' of an endpoint directly in the hub, in the sandbox
- 8 Understanding what the A_ prefix represents in the entity set names
- 9 Downloading and looking briefly at all the API specification documents JSON, YAML and EDMX
- 10 Fixing my neovim installation that I broke just before the live stream started
- 11 Staring at and exploring the EDMX the OData service metadata document for API_BUSINESS_PARTNER
- 12 Resorting to using Latin to convey what I'm trying to say #FAIL
- 13 Opening the API_BUSINESS_PARTNER.edmx file in VS Code
- 14 A great discussion on singular vs plural naming convention for entities
- 15 Opening the API_BUSINESS_PARTNER.edmx file with the OData CSDL Modeler extension - very diagram, much graphical, wow!
- 16 Kicking the tyres of the API from my own machine, with curl, working through the responses with an API key 401, then 307, and ultimately a binary gzipped payload
- 17 Distinguishing between the service document and the metadata document - the two "well known" documents of any OData service
- 18 Recognizing the origins of OData in the Atom syndication format XML elements
- 19 Fixing the name of the entity set we are reminded of the A2X nature of this API by the myriad annotations in the metadata
- 20 Importing the API_BUSINESS_PARTNER.edmx file into a new CAP Node.js project and having it mocked and served locally as an OData v4 service with our very own test data, with just one command and in o…
