Appearance
UDINA Core
UDINA Core forms the foundation for all SaaS applications, supporting both on-premise and cloud scenarios. Simply subscribe once and always benefit from the latest version—without the hassle of maintenance.
Key Features
- Fast and seamless onboarding
- Centralized access point for all applications
- Automatic and worry-free updates
- Consistent multi-device user experience
- Native integration with other services
UDINA Connect – Simple. Central. Connected.
UDINA Connect provides your B2B customers with a single, intuitive entry point that unifies all relevant functions in one place. Seamlessly integrating Commerce Cloud into the app shell, it offers role-based access, a consistent multi-device user experience, and faster access to tools—all fully aligned with your corporate branding. This streamlined approach not only boosts productivity but also strengthens your brand identity, builds trust, and fosters long-term business relationships.
Multitenancy
Multitenancy is one of the important architectural concept in cloud. SAP BTP allows to develop and run multitenant applications, and share them with multiple customers simultaneously. Fundamentals of Multitenancy in SAP BTP
Multi-tenancy is an architecture in which:
- A single instance of an application serves multiple customers
- Each customer is called a tenant
- Multiple customers (tenants) use the same computing resources – physically integrated but logically separated
- Even though customers share resources, customers aren't aware of each other, and their data is kept totally separate
To make sure, that all data is securly isolated, the following architecture is used:
Multitenant App
The solution is implemented and physically deployed in the UDINA Provider Subaccount. All Consumers get their own Subaccount, subscribing to the provider solution by completly isolating the customer infrastructure (like Cloud Connector for SAP S/4HANA OnPremise systems) and the identity provisioning.
Data Separation
The solutions uses Schema Separation to archieve data separation in multitenancy:
- A dedicated schema or if it's HANA an HDI Container.
- Recommended approach by sap.
- Very flexible - you can have a single database instance, for example a single HANA Cloud instance. Each tenant will get their own dedicated HDI Container. So effective their own schema and tables.
- Can easily backup individual schemes or HDI containers.
