From 716a06e4c11a960805c970e06668067ddef968ec Mon Sep 17 00:00:00 2001 From: Eckart Liemke Date: Fri, 18 Sep 2026 14:17:42 +0200 Subject: [PATCH 1/5] update MTX TMS documentation --- guides/multitenancy/index.md | 38 ++++++++++++++++++++++++++++-------- 1 file changed, 30 insertions(+), 8 deletions(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index ce6609f815..1abd56496f 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -818,10 +818,6 @@ cds watch --profile dev The SAP HANA Tenant Management Service (TMS) v2 service provides direct support for managing SAP HANA tenants. -> [!important] Be aware of the current limitations: -> - **Not suitable for existing applications** as there is **no migration from Service Manager** available yet. This will be provided as HANA tool later.
-> There **won't be support for both Service Manager and TMS v2** together in one application. - [For more information, see the SAP HANA documentation](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-multitenancy/introducing-sap-hana-cloud-multitenancy){.learn-more} [Find the TMS v2 API on the SAP Business Accelerator Hub](https://api.sap.com/api/TenantAPI/overview){.learn-more} @@ -982,13 +978,39 @@ To group the tenant containers of many applications or microservices in a common When you unsubscribe and the tenant container is deleted, the corresponding SAP HANA tenant isn't deleted as it could potentially still be in use for other applications. -#### Limitations +#### Migration of exisiting Service Manager based applications + +Please check the [SAP HANA documentation how to migrate tenant containers to HANA TMS v2](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-multitenancy/migrate-schema-or-hdi-container-to-database-tenant). +This migration will also be provided as a mass migration using the Automation Pilot soon. -There are still some limitations with the current client implementation. +##### Switch application to HANA TMS v2 -- **Database ID is Mandatory** - As mentioned, you need to specify a database ID that's to be used, either for all tenants or per subscription request, see [Deployment configuration](./mtxs#deployment-config). +Before you run the migration, you will need to create a HANA TMS v2 service with service plan `hana-multitenancy` to ensure the new containers are assigned to the right service instance. +To switch the application to HANA TMS v2 without redeploying the application, bind the HANA TMS v2 service to the application in addition to the Service Manager binding. +By using cds [configuration profiles in compination with the `CDS_ENV` environment variable](../../node.js/cds-env#profiles), you can switch to the HANA TMS v2 binding with a simple restart. +Example: +```jsonc +"cds": { + ..., + "requires": { + "db": { + "kind": "hana", + "vcap": { + "name": "application-db" + }, + "[hanatms]": { + "kind": "hana", + "vcap": { + "name": "application-db-tms" + } + } + }, + ... + } + } +``` +If you set the environment `CDS_ENV=hanatms`, the application will use HANA TMS v2 after the next restart. ## SaaS Dependencies {#saas-dependencies} Some of the xsuaa-based services your application consumes need to be registered as _reuse services_ to work in multitenant environments. This holds true for the usage of both the SaaS Registry service and the Subscription Manager Service (SMS). From 4e22c1e6ff553bf99d450eb18d56fe41d299bc78 Mon Sep 17 00:00:00 2001 From: ecklie <52252271+ecklie@users.noreply.github.com> Date: Fri, 18 Sep 2026 14:31:25 +0200 Subject: [PATCH 2/5] Apply batched suggestions from code review Co-authored-by: hyperspace-pr-bot[bot] <209611008+hyperspace-pr-bot[bot]@users.noreply.github.com> --- guides/multitenancy/index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index 1abd56496f..5c49a62a9d 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -978,16 +978,16 @@ To group the tenant containers of many applications or microservices in a common When you unsubscribe and the tenant container is deleted, the corresponding SAP HANA tenant isn't deleted as it could potentially still be in use for other applications. -#### Migration of exisiting Service Manager based applications +#### Migration of existing Service Manager-based applications -Please check the [SAP HANA documentation how to migrate tenant containers to HANA TMS v2](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-multitenancy/migrate-schema-or-hdi-container-to-database-tenant). -This migration will also be provided as a mass migration using the Automation Pilot soon. +Refer to the [SAP HANA documentation for migrating tenant containers to HANA TMS v2](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-multitenancy/migrate-schema-or-hdi-container-to-database-tenant). +SAP Automation Pilot will also support this migration as a mass migration. ##### Switch application to HANA TMS v2 Before you run the migration, you will need to create a HANA TMS v2 service with service plan `hana-multitenancy` to ensure the new containers are assigned to the right service instance. To switch the application to HANA TMS v2 without redeploying the application, bind the HANA TMS v2 service to the application in addition to the Service Manager binding. -By using cds [configuration profiles in compination with the `CDS_ENV` environment variable](../../node.js/cds-env#profiles), you can switch to the HANA TMS v2 binding with a simple restart. +Use [`cds` configuration profiles with the `CDS_ENV` environment variable](../../node.js/cds-env#profiles) to switch to the HANA TMS v2 binding with a restart. Example: ```jsonc @@ -1010,7 +1010,7 @@ Example: } } ``` -If you set the environment `CDS_ENV=hanatms`, the application will use HANA TMS v2 after the next restart. +If you set the `CDS_ENV` environment variable to `hanatms`, the application uses HANA TMS v2 after the next restart. ## SaaS Dependencies {#saas-dependencies} Some of the xsuaa-based services your application consumes need to be registered as _reuse services_ to work in multitenant environments. This holds true for the usage of both the SaaS Registry service and the Subscription Manager Service (SMS). From 70b100c3e5fc6a15ebf262a60b2dc43dd1b7f9fd Mon Sep 17 00:00:00 2001 From: Eckart Liemke Date: Fri, 18 Sep 2026 15:12:23 +0200 Subject: [PATCH 3/5] update switch hint --- guides/multitenancy/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index 5c49a62a9d..41f20daff0 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -985,7 +985,9 @@ SAP Automation Pilot will also support this migration as a mass migration. ##### Switch application to HANA TMS v2 -Before you run the migration, you will need to create a HANA TMS v2 service with service plan `hana-multitenancy` to ensure the new containers are assigned to the right service instance. +As described in the migration documentation, you need to create a HANA TMS v2 service with service plan `hana-multitenancy` before the migration to ensure the new containers are assigned +to the right service instance. + To switch the application to HANA TMS v2 without redeploying the application, bind the HANA TMS v2 service to the application in addition to the Service Manager binding. Use [`cds` configuration profiles with the `CDS_ENV` environment variable](../../node.js/cds-env#profiles) to switch to the HANA TMS v2 binding with a restart. From 56428791af23af6281c014c8bf6bf0650bf8bb87 Mon Sep 17 00:00:00 2001 From: Eckart Liemke Date: Mon, 21 Sep 2026 17:27:38 +0200 Subject: [PATCH 4/5] hint for migration section --- guides/multitenancy/index.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index 41f20daff0..b5a4613177 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -821,6 +821,12 @@ The SAP HANA Tenant Management Service (TMS) v2 service provides direct support [For more information, see the SAP HANA documentation](https://help.sap.com/docs/hana-cloud/sap-hana-cloud-multitenancy/introducing-sap-hana-cloud-multitenancy){.learn-more} [Find the TMS v2 API on the SAP Business Accelerator Hub](https://api.sap.com/api/TenantAPI/overview){.learn-more} +:::info Migration of existing applications +The configuration changes that are decscribed here also apply for existing applications that you want to migrate to HANA TMS v2. + +The migration of existing tenant containers to HANA TMS v2 is described in the [Migration section](#migration-of-existing-service-manager-based-applications). +::: + #### Configure MTXS for Tenant Management Service This documentation uses the bookshop sample to showcase necessary configuration. From bdf85e6e636b68a5b91e15bc13bf65664967ee59 Mon Sep 17 00:00:00 2001 From: ecklie <52252271+ecklie@users.noreply.github.com> Date: Mon, 21 Sep 2026 17:38:37 +0200 Subject: [PATCH 5/5] Update guides/multitenancy/index.md Co-authored-by: hyperspace-pr-bot[bot] <209611008+hyperspace-pr-bot[bot]@users.noreply.github.com> --- guides/multitenancy/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guides/multitenancy/index.md b/guides/multitenancy/index.md index b5a4613177..a66e2c9483 100644 --- a/guides/multitenancy/index.md +++ b/guides/multitenancy/index.md @@ -822,7 +822,7 @@ The SAP HANA Tenant Management Service (TMS) v2 service provides direct support [Find the TMS v2 API on the SAP Business Accelerator Hub](https://api.sap.com/api/TenantAPI/overview){.learn-more} :::info Migration of existing applications -The configuration changes that are decscribed here also apply for existing applications that you want to migrate to HANA TMS v2. +The configuration changes described here also apply to existing applications that you want to migrate to HANA TMS v2. The migration of existing tenant containers to HANA TMS v2 is described in the [Migration section](#migration-of-existing-service-manager-based-applications). :::