cdse
Resolves a destination from a CAP project's own configuration, then makes the outbound call with axiosaxiosA promise-based HTTP client for the browser and Node.js, and the client a CAP module here hands an outbound request to once the destination has been resolved.: the url, the method and the body are written at the call site.
cdse.connect.to("NorthWind") returns a service object whose run() takes a url, an HTTP method and a body and passes them to axiosaxiosA promise-based HTTP client for the browser and Node.js, and the client a CAP module here hands an outbound request to once the destination has been resolved.. The module handles the destination and connectivity configuration and reads the CDS configuration in package.json, so the address and the credentials stay out of the code. Setting csrfProtection: true on a write adds the X-CSRF-Token round trip. What the README documents ends at the call: there is no imported service definition and no generated client, so each url and payload is written where it is used.
Facts
Where it sits
Who is behind it
In the atlas: maintains 1, contributes to 1, wrote 3@jcailanmaintainerbryan-weeContributes to this
In the atlas: contributes to 1@bryan-wee1 contributor
Before choosing this
Signals
ActivityQuietRelease and repository quiet for 46 months
Both observable publication channels have been quiet for at least 24 full months. This may be normal for stable software; check whether its current state still fits your use.
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
- Independently maintained
- Runtime
- Node.js
As a package
- Where it runs
- does not say
- Distributed through
- npm
Connections
Reaching remote systems without addresses or credentials in the code
CAP Node.js runtime
A promise-based HTTP client for the browser and Node.js, and the client a CAP module here hands an outbound request to once the destination has been resolved.
Download
Install
npm add cdseDerived from the package name. No recipe recorded; the README has the configuration.
Where it sits in your app
Download
README
quoted from jcailan/cdse under MIT, readCDSE Node Module 
CDS Extension for External Service Consumption
This node module provides an alternative solution for consuming external services in a Cloud Application Programming (CAP) Model where the users can use the raw capabilities of axios node module while still utilizing the following capabilites of CAP framework:
- Fluent api concept
- Handling of Destination and Connectivity configurations
- CDS configuration found in package.json
Installation
Using npm:
> npm install cdseExample
const cdse = require("cdse");
const service = await cdse.connect.to("NorthWind");
// HTTP GET
let result = await service.run({
url: "/Products"
});
// HTTP POST
result = await service.run({
url: "/Products",
method: "post",
data: {
ID: 1234,
ProductName: "Milk"
}
});
// HTTP POST with X-CSRF-Token protection
result = await service.run({
url: "/Products",
method: "post",
data: {
ID: 1234,
ProductName: "Milk"
},
csrfProtection: true
});History
Notes
Revised GitHub Actions workflows
Notes
Adjust GitHub Actions workflow
Notes
Fixed issue when publishing to npm with --tag
Notes
Fixed npm release version
Notes
Switch to GitHub Actions
Notes
Switched to GitHub Actions
Notes
Fixed the undefined username and password
Other 1
Notes
- Add Travis CI config (#2) 10c5bbb
Other 3
Notes
- Updated package-lock.json 31a6d95
- Updated package.json d633d94
- Added unit tests 28b8837
Other 9
Notes
- Update test script to avoid failing np 970e79a
- Update package version to 1.0.7 2d23624
- Fixed bug on X-CSRF-Token handling 5904a70
- Added support for X-CSRF-Token validation c0400c3
- Fixed bug where local config was not recognized a7f1b91
- Added checks for unsupported scenario 90c2c52
- Fixed bug on SCC Location ID configuration c370d8c
- Added support for Cloud Connection with LocationId cdfd573
- Fixed request header issue 1c162df
https://github.com/jcailan/cdse/compare/efbff6fe0b61c1465da9f4c12ac5db12d3c2c617...v1.0.8
Others providing
Compare all 15 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 runtimefrom BTP/BAIP
- SAP Private Link ServiceSAP Private Link ServiceA private network connection between a selected SAP BTP service and a selected service in an application's own account with a partner cloud provider, so the traffic between them never touches the public internet.sap official, btpPrivate network link between a BTP service and a partner cloudfrom BTP/BAIP
- 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 Javafrom CAP
- com.sap.cds:cds-integration-cloud-sdkcom.sap.cds:cds-integration-cloud-sdkA 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.sap official, capSAP Cloud SDK integration for remote REST services in CAP Javafrom CAP
- 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 projectsfrom CAP
- @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 runtimefrom CAP
- @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 SDKfrom CAP
- @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 credentialsfrom CAP
- @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 clientsfrom CAP
- @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 SDKfrom CAP
- @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 callsfrom CAP
- @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 packagesfrom CAP
- btp-cloud-connector-setup-automationbtp-cloud-connector-setup-automationA Yeoman generator that adds the Cloud Connector system mappings for an XS Advanced system and writes the matching SAP BTP destination files.sap official, btpYeoman generator for Cloud Connector mappings and BTP destinationsfrom BTP/BAIP
- @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 destinationfrom CAP
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
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:cdse- JSON
- /artifacts/cdse.json
- MCP
- Connecting an agent