CapabilityOperations & RuntimeJava, read from its artifacts

Multitenancy

Serving many tenants from one deployment — onboarding, tenant-isolated data, per-tenant schema deployment and the operational tooling around it. It is decided once, before anything is built, and narrows the artifacts in almost every capability downstream: most sharply in caching and anything else holding state in process.

Showing artifacts, examples and content with confirmed Java applicability. View All CAP

Overview

SAP SHIPS

com.sap.cds:cds-feature-mt

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.

SourceBuilding Applications — capirechecked 2026-09-19

com.sap.cds:cds-services-bom

Carries the tenant in the Request Context across every service call and thread, and opens tenant-specific database connections from it. Provisioning and subscription are cds-feature-mt.

SourceRequest Contexts — capirechecked 2026-09-27

A Java coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS

No community artifact is confirmed here for Java.

A Java coverage assessment has not been written. View all flavors

Artifacts3

3 of 3 artifacts

ArtifactSignals

Packages2

com.sap.cds:cds-feature-mtMultitenancy for CAP Java: tenant lifecycle and per-tenant containers

Signals

none

com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versions

Signals

none

Services1

SAP Software-as-a-Service Provisioning serviceRegisters a multitenant application for subaccount subscriptions

Signals

none

Details

Coverage

statecore only, CAP, Java, derived

domainOperations & Runtime

also inBTP/BAIP

For your agent

Ref: capability:multitenancy
JSON: /capabilities/multitenancy.json
MCP: Connecting an agent