CapabilityIntegration & MessagingJava, 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 Java applicability. View All CAP

Overview

SAP SHIPS
com.sap.cds:cds-feature-remote-odata

Serves a remote OData V2 or V4 API as a CAP Remote Service in CAP Java: configured with the service definition from the CDS model and a destination or service binding, a CQN query against it is translated into the OData request.

A Java coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

No community artifact is confirmed here for Java.

A Java coverage assessment has not been written. View all flavors

Artifacts1

1 of 1 artifacts
ArtifactSignals
Packages1
com.sap.cds:cds-feature-remote-odataRemote Services for consuming OData V2 and V4 APIs in CAP Java
Signals
none

Seen working1

ArtifactSignals
Samples1
cap-java-resilienceCAP Java service consuming a Business Partner API mocked in Node.js
No license

Details

Coverage
statecore only, CAP, Java, derived
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