com.sap.cds:cds-integration-cloud-sdk
A CAP Java feature that integrates the SAP Cloud SDK, so features such as remote OData and enterprise messaging resolve a destination or service binding and reach a remote REST-based service.
Integrates the SAP Cloud SDK into the CAP Java runtimecom.sap.cds:cds-services-bomThe Maven bill of materials for CAP Java, pinning every com.sap.cds module in a release, from the API and core runtime to the Spring Boot starters and the CQN engine, to the same version.sap official, cap so a feature can resolve a destination or a service binding and reach a remote REST-based service through it. The CAP Java SDK ships only the minimum Cloud SDK dependencies by default; this feature is what com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, cap and com.sap.cds:cds-feature-enterprise-messagingcom.sap.cds:cds-feature-enterprise-messagingA CAP Java feature that connects a CAP messaging service to SAP Event Mesh, activated by setting the service's kind to enterprise-messaging, and looks up the bound instance.sap official, cap build on for destination and binding resolution. CAP Java 2.6.0 and higher works with Cloud SDK versions 4 and 5, defaulting to Cloud SDK 4 for backward compatibility unless the application adds a newer Cloud SDK connectivity dependency itself.
Facts
Where it sits
Before choosing this
Conditions
LicenceSAP Developer License Agreement 3.2 CAP§ 1from DestinationsA destination used by a covered CAP application sends SAP product data to a non-SAP product rather than only addressing a remote endpoint.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
A destination is configuration, not the deciding boundary. The licence becomes material when the resulting data flow is extraction into a non-SAP product, so the target and purpose need review.
SAP Developer License Agreement 3.2 CAP →What it declares
Every artifact
- Type
- Package
- Origin
- By SAP
- Runtime
- Java
As a package
- Where it runs
- does not say
- Distributed through
- does not say
Connections
Reaching remote systems without addresses or credentials in the code
Remote Services for consuming OData V2 and V4 APIs in CAP Java
Download
Others providing
Compare all 13 on the Destinations page →- SAP Destination serviceSAP Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btpNamed, credentialed addresses of other systems resolved at runtime
- com.sap.cds:cds-feature-remote-odatacom.sap.cds:cds-feature-remote-odataA CAP Java feature for consuming remote OData V2 and V4 services as Remote Services, translating CQN queries into OData requests against a destination or a service binding.sap official, capRemote Services for consuming OData V2 and V4 APIs in CAP Java
- capire/s4capire/s4A pre-built integration package for SAP S/4HANA, holding the imported service definitions a CAP project would otherwise generate for itself.sap official, capPrebuilt SAP S/4HANA integration package for CAP projects
- cdsecdseResolves a destination from a CAP project's own configuration, then makes the outbound call with axios: the url, the method and the body are written at the call site.independent, capDestination resolution and axios calls from CAP configuration
- @sap/cds@sap/cdsThe CAP Node.js runtime, which compiles the CDS model, serves the services declared in it, answers generic requests before any handler runs, and loads every cds-plugin.sap official, capCAP Node.js runtime
- @sap-cloud-sdk/connectivity@sap-cloud-sdk/connectivityDestination lookup and the connectivity proxy — the package that turns a destination name into a reachable endpoint with credentials attached.sap official, capDestination lookup and connectivity proxy for the Cloud SDK
- @sap-cloud-sdk/http-client@sap-cloud-sdk/http-clientThe HTTP client that carries a destination's credentials, so an outbound call inherits the authentication rather than assembling it.sap official, capHTTP client carrying a destination's credentials
- @sap-cloud-sdk/odata-common@sap-cloud-sdk/odata-commonThe shared machinery under the SDK's OData and OpenAPI client generators; a dependency of the generated clients rather than something written against directly.sap official, capShared machinery under the Cloud SDK's OData and OpenAPI clients
- @sap-cloud-sdk/openapi@sap-cloud-sdk/openapiGenerated OpenAPI clients for the Cloud SDK, so a REST API described by a specification is called through typed functions.sap official, capGenerated OpenAPI clients for the Cloud SDK
- @sap-cloud-sdk/resilience@sap-cloud-sdk/resilienceTimeouts, retries and circuit breaking around a remote call, so one slow downstream system does not take the application with it.sap official, capTimeouts, retries and circuit breaking around remote calls
- @sap-cloud-sdk/util@sap-cloud-sdk/utilGeneral utilities shared across the Cloud SDK packages — a dependency, not a thing to reach for on its own.sap official, capGeneral utilities shared across the Cloud SDK packages
- @sapmentors/cds-scp-api@sapmentors/cds-scp-apiA Node module for CAP that calls an external API through a destination instead of a hardcoded endpoint, taking its address, credentials and on-premise tunnel from the SAP Destination and Connectivity services.community org, capNode module for CAP calling external APIs through a destination
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“Integration of SAP Cloud SDK into CDS Services Java” — com.sap.cds:cds-integration-cloud-sdk — POM (5.1.1)
History in the atlas
- Allows integration with Cloud SDK to connect with remote REST-based services, only including the minimum Cloud SDK dependencies by default so a feature adds the rest as needed.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-integration-cloud-sdk- JSON
- /artifacts/cap-java-cds-integration-cloud-sdk.json
- MCP
- Connecting an agent