onedevatlasBeta
Browse the atlas
AllCAPABAPUI5BTP
All CAPNode.jsJava
CapabilityProtocols & APIsNode.js, read from its artifacts

OData

Serving a model as OData — V4, which CAP generates by default from CDS, and V2 for the clients that cannot move: older Fiori applications, SAPUI5 smart controls and integrations built against V2.

Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP

Overview

SAP SHIPS
@sap/cds

Serves every exposed service as OData V4 from the model with no adapter in between, and OData V2 through its proxy.

SourceService Protocols in CAP — capirechecked

A Node.js coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

A Node.js coverage assessment has not been written. View all flavors

Artifacts5

5 of 5 artifacts
ArtifactSignals
Build tools1
@root3287/cap-segwCompiler from a CDS service to SEGW model and data provider classes
Signals
Functional boundary
CDS plugins3
@cap-js-community/odata-v2-adapterExposes a CAP service as OData V2
Signals
none
@odatano/coreCAP plugin serving the Cardano blockchain as OData V4
Signals
none
@odatano/nightgateCAP plugin indexing the Midnight blockchain, exposed as OData V4
Signals
none
Packages1
@sap/cdsCAP Node.js runtime
Signals
none

Seen working3

ArtifactSignals
Samples3
bookshop-demoSimple CDS bookshop model used across CAP explanations
No license
SAP-samples/odata-dd-serverCAP Node.js server behind the OData Deep Dive tutorials
none
ui5-call-actionUI5 apps calling CAP OData actions and functions from custom code
No license

Details

Coverage
statecore and community, CAP, Node.js, derived
domainProtocols & APIs
also inABAP
Comparison properties1

These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.

Protocols
For your agent
Ref
capability:odata
JSON
/capabilities/odata.json
MCP
Connecting an agent