SampleSampleA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cap-agent-ui5-webui-sample
A worked example of the cap-agent-ui5-webuicap-agent-ui5-webuiGives a CAP agent a UI5 web interface out of the box, so an agent built in the service has somewhere to be talked to without a separate frontend project.independent, cap plugin, shown running locally, in hybrid mode against SAP AI Core, and deployed.
Facts
Last push
Where it sits
Lives in
Demonstrates
Agent toolingCAPAgent toolingBuilding an agent into your own application — the tools it may call, the state it keeps between turns, and the framework it runs in. Distinct from MCP servers, which expose an application to somebody else's agent, and from agent guidance, which is knowledge handed to a coding agent.LLM integrationCAPLLM integrationCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.
Flavors
Node.jsfrom its runtime
Who is behind it
Wouter LemaireWouter LemaireMaintains this
In the atlas: maintains 25, contributes to 39, wrote 12@lemaiwomaintainer
In the atlas: maintains 25, contributes to 39, wrote 12@lemaiwomaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
- Runtime
- Node.js
As a sample
- Form
- does not say
Connections
Group by
NodeRelationBasis
Functional
Agent toolingAgent toolingBuilding an agent into your own applicationSAP and community, unassessed
demonstrates
authored
demonstrates Agent tooling
Building an agent into your own application
LLM integrationLLM integrationCalling a language model with tenant and credential handling solvedSAP and community, narrow by design
demonstrates
authored
demonstrates LLM integration
Calling a language model with tenant and credential handling solved
Download
Architecture
as mta.yaml states it at 3f71183, readDownload
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
SAP HTML5 Application Repository service for SAP BTPStores built UI5 and HTML5 applications and serves them at runtime through the approuter, so an app ships no static server of its own.sap official, btp
sample-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
sample-router → sample-srvStated in the descriptor, datamta.yaml, module sample-router, requires srv-api
sample-router → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, OAuth 2.0, outboundLogging a user in on the routes that require it: the router runs the OAuth2 authorization code flow against the UAA and takes the redirect back at its login callback endpoint.
sample-router → SAP HTML5 Application Repository service for SAP BTPStated in the descriptor, data, outboundFetching the static content and the xs-app.json routes of an HTML5 application the repository holds, to serve them.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- sample-srvhana, sample-aicore
- sample-db-deployerhana
- sample-app-contentSAP HTML5 Application Repository service for SAP BTP
Documented, with no instance in the document
- @cap-js/agents requires SAP AI Coresample-srvconditionalThe model the agent calls on each turn of its loop, reached through an SAP AI Core service instance.CAP-level Agents, cds.requires.llm — capire
The default for `production` and `hybrid`, connects to SAP AI Core
CAP-level Agents, cds.requires.llm — capireThe LLM used by an agent is configured via `cds.requires.llm`.
- @cap-js/hana requires SAP HANA Cloudsample-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicessample-srv
- @sap/approuter requires Cloud Identity Servicessample-routerAuthenticating the user against Identity Authentication instead of, or alongside, SAP Authorization and Trust Management service. Bound to both, the router picks IAS.@sap/approuter 23.0.0 — README, authenticationType
Bound to both services: prefers ias if both authentication services can be used in the current subaccount, determined via BTP security endpoint (may impact response time)
- @sap/approuter requires SAP Destination servicesample-routerReading the destination a route forwards to, where that configuration is not written into the router's own environment.@sap/approuter 23.0.0 — README, destination configuration
Destination configuration can also be read from `destination service`.
- @sap/approuter requires SAP Connectivity servicesample-routerForwarding to an on-premise backend: the binding is required once a destination sets its ProxyType to on-premise.@sap/approuter 23.0.0 — README, destination ProxyType
if ProxyType set to `on-premise`, binding to SAP Cloud Platform connectivity service is required.
Bound in the descriptor, not joined to an entry
hana
README
quoted from lemaiwo/cap-agent-ui5-webui-sample, readlemaiwo/cap-agent-ui5-webui-sample/README.mdthe maintainer’s wordsOn GitHub
cap-agent-ui5-webui-sample
A small CAP application that uses the
cap-agent-ui5-webui plugin, showing
the three ways you would actually run it: locally, hybrid against a real LLM on SAP
AI Core, and deployed to SAP BTP Cloud Foundry.
The domain is a tiny support desk — customers and tickets, with an escalate action gated
behind human approval. Swap it for your own; nothing about the plugin changes.
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
runtimesnode
discovered viaGitHub API · lemaiwo
first seen in the atlas
ecosystem and domaincap, ai-and-agents
History in the atlas
- First seen.
For your agent
- Ref
artifact:lemaiwo-cap-agent-ui5-webui-sample- JSON
- /artifacts/lemaiwo-cap-agent-ui5-webui-sample.json
- MCP
- Connecting an agent