How to design the tenant isolation mechanism of SAP Hybris and Netweaver

Today, I will talk to you about how to design the tenant isolation mechanism of SAP Hybris and Netweaver. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something from this article.

The tenant isolation in ABAP is distinguished by the client ID of DB table.

Hybris also has multi tenant's concept:

Typical usage scenarios for Hybris multi tenant:

(1) hosting SAP Hybris Commerce for multiple individual customers

(2) A single, company-wide SAP Hybris Commerce that provides services to countries through individual products and customer data

(3) use the SAP Hybris Commerce CMS module to power the country-specific version of the company's website

Define which tenant is supported on a Hybris server in project.properties under project folder:

Tenant isolation in Hybris is realized through table name prefix.

Different tenant needs to define different table prefix:

Naming convention: tenant_.properties of the configuration file:

How table prefix is defined in .properties:

Manage tenant in admin console:

After reading the above, do you have any further understanding of how to design the tenant isolation mechanism for SAP Hybris and Netweaver? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.