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 →
mtxs-reviews
Multitenant CAP application using cds-mtxs.
Facts
Last push
Where it sits
Lives in
Demonstrates
MultitenancyCAPMultitenancyServing 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](capability:caching) and anything else holding state in process.Tenant extensibilityCAPTenant extensibilityLetting a customer extend the model of a running SaaS application with extra fields and entities per tenant, without forking the application, as distinct from extending the application's code for every customer at once.
Who is behind it
Gregor WolfGregor WolfMaintains this
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainer
In the atlas: maintains 17, contributes to 59, wrote 2@gregorwolfmaintainer
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
As a sample
- Form
- A reference application
Connections
Group by
NodeRelationBasis
Functional
MultitenancyMultitenancyServing many tenants from one deploymentSAP and community, narrow by design
demonstrates
authored
demonstrates Multitenancy
Serving many tenants from one deployment
Tenant extensibilityTenant extensibilityLetting a customer extend a running SaaS model per tenantSAP and community, unassessed
demonstrates
authored
demonstrates Tenant extensibility
Letting a customer extend a running SaaS model per tenant
Download
Architecture
as mta.yaml states it at 03a66a4, 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 Destination serviceNamed, credentialed addresses of other systems, resolved at runtime — so an application holds no URL and no secret of its own, and the same code reaches a different system in every landscape.sap official, btp
SAP Service ManagerThe BTP registry for service brokers and environments: consumes SAP BTP services from any connected runtime environment, tracks the service instances created, and shares them between environments.sap official, btp
SAP 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, btp
mtxs-reviews-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.
mtxs-reviews-srv → mtxs-reviewsStated in the descriptor, datamta.yaml, module mtxs-reviews-srv, requires app-api
mtxs-reviews → mtxs-reviews-srvStated in the descriptor, datamta.yaml, module mtxs-reviews, requires srv-api
mtxs-reviews → 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.
mtxs-reviews → SAP Destination serviceDocumented only, data, outboundReading the configuration of the destination a route forwards to, where the router's own environment does not define it.
SAPnot SAP's, or the project's ownauthenticationstated in the documentdocumented only
Bound, and not drawn
- mtxs-reviews-srvSAP Service Manager, mtxs-bookshop-db, SAP Software-as-a-Service Provisioning service, SAP Destination service, mtxs-bookshop-srv-api
Documented, with no instance in the document
- @sap-cloud-sdk/connectivity requires SAP Connectivity servicemtxs-reviews-srv
- @sap/xssec requires Cloud Identity Servicesmtxs-reviews-srv
- @sap/approuter requires Cloud Identity Servicesmtxs-reviewsAuthenticating 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 Connectivity servicemtxs-reviewsForwarding 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.
- @sap/approuter requires SAP HTML5 Application Repository service for SAP BTPmtxs-reviewsServing static content from the repository rather than from the router's own folder. Bound, both the files and the xs-app.json routes come from there.@sap/approuter 23.0.0 — README, Integration with HTML5 Application Repository
When the application router interacts with HTML5 Application Repository to serve HTML5 Applications, all static content and routes (xs-app.json) are retrieved from HTML5 Application Repository.
README
quoted from gregorwolf/mtxs-reviews, readgregorwolf/mtxs-reviews/README.mdthe maintainer’s wordsOn GitHub
Multitenant CAP Reviews
This project demonstrates the integration to another CAP multitenant application using HANA Synonyms. The application providing the Books entity is mtxs-bookshop. The mtxs-bookshop defines HANA Roles (BOOKSHOP.hdbrole and BOOKSHOP_O.hdbrole) that allow this app to access the HANA Table MY_BOOKSHOP_BOOKS.
To achieve this functionality in a multitenant application we make use of a dynamically defined user provided service that gets its credentials from the service manager instance of the mtxs-bookshop app.
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
discovered viaGitHub API · gregorwolf
first seen in the atlas
ecosystem and domaincap, operations-and-runtime
History in the atlas
- A sample's domain recorded what kind of thing it is, which artifact_type already says, so it sat under Learning while the capability it demonstrates sat elsewhere — filtering a domain for a worked example returned nothing. Domain now follows the single capability the sample demonstrates; a sample with no single subject stays in Learning.
- First seen.
For your agent
- Ref
artifact:gregorwolf-mtxs-reviews- JSON
- /artifacts/gregorwolf-mtxs-reviews.json
- MCP
- Connecting an agent