com.sap.cds:cds-feature-mt
The CAP Java feature that makes a Maven application multitenant aware: tenant lifecycle events, per-tenant database containers, and the wiring to the Node.js MTX sidecar.
Adds multitenancy to a CAP Java application built on com.sap.cds:cds-services-bomcom.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: the runtime exposes SUBSCRIBE, UNSUBSCRIBE and DEPENDENCIES tenant events an application can hook with custom handlers, and by default creates or deletes a tenant-specific database container through the SAP BTP Service Manager on subscribe and unsubscribe. It stops at the Java backend: CDS model data might need to be fetched from the MTX sidecar in case of tenant extensions, so a multitenant CAP Java deployment still runs the Node.js @sap/cds-mtxs@sap/cds-mtxsMultitenancy, tenant provisioning and model extensibility for CAP.sap official, cap sidecar alongside it. cds add multitenancy wires both sides at once, adding this Maven dependency with runtime scope to srv/pom.xml and a sidecar URL to the application's configuration. Switching the tenant in the request context is comparatively expensive for exactly that reason.
Facts
Where it sits
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
Serving many tenants from one deployment
Multitenancy, tenant provisioning and extensibility for CAP
Download
Others providing
Compare all 7 on the Multitenancy page →- SAP Software-as-a-Service Provisioning serviceSAP Software-as-a-Service Provisioning serviceRegisters a multitenant application so that subaccounts can subscribe to it, and calls the application back on every subscribe and unsubscribe.sap official, btpRegisters a multitenant application for subaccount subscriptionsfrom BTP/BAIP
- com.sap.cds:cds-services-bomcom.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, capMaven bill of materials pinning CAP Java module versionsfrom CAP
- @cap-js-community/mtx-tool@cap-js-community/mtx-toolCLI for operating multitenant CAP applications — inspecting, upgrading and repairing tenants across a landscape.community org, capCLI for operating tenants of multitenant CAP applicationsfrom CAP
- @sap/cds-mtxs@sap/cds-mtxsMultitenancy, tenant provisioning and model extensibility for CAP.sap official, capMultitenancy, tenant provisioning and extensibility for CAPfrom CAP
- @sap/cds-oyster@sap/cds-oysterRuns tenant-specific extension code inside a WebAssembly sandbox, so a SaaS application can accept custom logic from a customer without running it unguarded.sap official, capWebAssembly sandbox for tenant-specific extension code in CAPfrom 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
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
“CAP Java comes with a rich set of prepared modules for all different layers of the stack:” — Building Applications — capire
History in the atlas
- Exposes SUBSCRIBE, UNSUBSCRIBE and DEPENDENCIES tenant lifecycle events and by default creates or deletes a tenant-specific database container through the Service Manager; CDS model data for tenant extensions is fetched from the Node.js MTX sidecar rather than handled here.
- First seen.
For your agent
- Ref
artifact:cap-java-cds-feature-mt- JSON
- /artifacts/cap-java-cds-feature-mt.json
- MCP
- Connecting an agent