onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
All CAPNode.jsJava
CapabilityIntegration & MessagingNode.js, read from its artifacts

Service integration

Using a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from destinations, which is how the address and the credentials are found, and from replication, which is holding the data locally.

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

Overview

SAP SHIPS
@sap/cds-dk

cds import converts an OData EDMX, an OpenAPI or an AsyncAPI file to CSN, the model of the remote service a consuming project then connects to; cds.import does the same from JavaScript.

SourceCDS Import API — capirechecked
@sap/cds

Builds a remote proxy with cds.connect.to for any imported service, translates a local query into OData V4, OData V2 or HCQL against the remote entity, and mocks the imported service in process until a binding is configured; outbound calls use the SAP Cloud SDK client when installed, else the native fetch client.

SourceCAP-Level Service Integration — capirechecked

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

THE COMMUNITY ADDS
cds-data-federation

Delegates a consumption view to its remote service from an annotation, with the query translated, writes opt-in, and $expand and navigation across the local and remote boundary handled in the plugin rather than in a handler per scenario.

Sourcecds-data-federation — READMEchecked

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

Artifacts3

3 of 3 artifacts
ArtifactSignals
CDS plugins1
cds-data-federationData federation for CAP via delegation, caching and replication
Signals
none
CLI tools1
@sap/cds-dkCommand line client and development toolkit for CAP
Signals
none
Packages1
@sap/cdsCAP Node.js runtime
Signals
none

Shared tasks involving this capability1

Access an external system through an application MCP service

An AI agent queries external system data or invokes selected external operations through an application-owned service contract exposed over MCP.

Capabilities in this task

2 scoped assessments in CAP Node.js. Implementation conditions and evidence stay under Serve your application over MCP.

View scoped assessments

Content2

Group by
Piece, what it offers
cds-data-federation2
Federating, Replicating, and Caching Remote Data in CAP — Part 2
SAP Community, Mike Zaschka, part 2 of 2, BlogThe reasoningA recipeRunnable code
The Full Picture: Federating, Replicating, and Caching Remote Data in CAP — Part 1
SAP Community, Mike Zaschka, part 1 of 2, BlogThe reasoning

Seen working5

ArtifactSignals
Samples5
auth-samplesCAP services and a UI for trying role restrictions with mock users
No license
cap-external-northwindCAP service serving Northwind's external OData Products as its own
none
cap-java-resilienceCAP Java service consuming a Business Partner API mocked in Node.js
No license
cap-openaiCAP service actions calling OpenAI chat completions two ways
No license
cap-principal-propagationOn-premise ABAP OData V2 service read from CAP over Connectivity
No license

Details

Coverage
statecore and community, CAP, Node.js, derived
domainIntegration & Messaging
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:service-integration
JSON
/capabilities/service-integration.json
MCP
Connecting an agent