Everything in CAP / Java
Type
Domain
Origin: SAP official
Signals: No date
Java: Answers in Java
More
Group by: None
API proxies with security and traffic policies and Developer Hub
Identity Authentication and Identity Provisioning as one tenant
A2A adapter turning a CAP Java service into an LLM-backed agent
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
CAP Java handler for SAP Audit Log service API version 2
Change log of annotated entity fields for CAP Java
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Browser dashboard for a running CAP Java service during development
Connects CAP Java messaging to SAP Event Mesh
Declarative status-transition flows on bound actions in CAP Java
SAP HANA Cloud datasource for CAP Java applications
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
JDBC runtime for H2 and SQLite in CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Connects CAP Java messaging to Apache Kafka
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
PostgreSQL datasource for CAP Java applications
Beta connector from CAP Java messaging to Redis Pub/Sub
Remote Services for consuming OData V2 and V4 APIs in CAP Java
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
SAP Cloud SDK integration for remote REST services in CAP Java
Maven plugin running CDS build steps in a CAP Java project
Maven archetype generating a new CAP Java project
Maven bill of materials pinning CAP Java module versions
Managed queues and topics over AMQP, MQTT and REST
SAP's managed environment for building custom agents and workflows
Low-code SAP Build capability for custom Joule skills and agents
Binding onto hyperscaler object storage, chosen by plan
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed Redis from the hyperscaler via a BTP service binding
AI runtime on BTP with the Generative AI Hub
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Ingests and retains compliance audit data from BTP
OAuth server issuing JWTs and holding scopes for BTP apps
Cloud Foundry runtime of SAP BTP for polyglot applications
Development environment on BTP for UI5, Fiori, mobile and CAP
Proxy from cloud apps to on-premise systems via Cloud Connector
Predefined CI/CD pipelines for SAP development projects
Vault for an application's passwords, keys and keyrings
Named, credentialed addresses of other systems resolved at runtime
Extracts header fields and line items from business documents
APIs and a UI5 component for document management in apps
Boolean and string flags read by applications at runtime
SAP's relational database platform, on-premise and in HANA Cloud
For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Stores UI5 and HTML5 apps and serves them through the approuter
Event streaming and management platform in Integration Suite
Calls an application endpoint on a schedule and logs each run
SAP's AI engagement layer across SAP applications
Scans uploaded files over REST with ClamAV
Registers a multitenant application for subaccount subscriptions
One inbox for tasks across SAP applications and BTP workflows