Destinations
A UI5 app calls a path on its own origin, and whatever serves it maps that path to a destination. On this door the question is the dev server: reaching the same system the deployed route names without writing its address into the project.
Overview
SAP's backend-proxy-middleware forwards a path of the UI5 dev server to a backend named by destination instead of a URL, optionally read by a given Destination service instance through destinationInstance, with forwarded headers for a destination that uses principal propagation.
Not covered: In SAP Business Application Studio. Its README makes the backend URL mandatory unless a destination is given and the proxy runs there, so on a local machine the address is written into ui5.yaml.
ui5-middleware-destinationui5-middleware-destinationA UI5 Tooling server middleware that proxies requests to backends named in WebIDE-style destination files and serves the routes of a neo-app.json, with Basic Authentication only.independent, ui5 reads destinations from WebIDE-style destination files kept outside the project and answers the routes of neo-app.json with them, and ui5-middleware-approuterui5-middleware-approuterA UI5 CLI middleware that puts @sap/approuter in front of the UI5 dev server, proxying it to Cloud Foundry or XS Advanced destinations during development.community org, ui5 connects the dev server through @sap/approuter@sap/approuterSAP's Node.js application router: the single entry point in front of a business application's microservices, which authenticates the user, forwards each request to a backend by route and serves static content.sap official, btp to Cloud Foundry or XS Advanced destinations.
Artifacts
Nothing is mapped here yet.
Details
Coverage
For your agent
- Ref
capability:destinations- JSON
- /capabilities/destinations.json
- MCP
- Connecting an agent