Managing Tenant Connections

The Manage Tenant Connections application is integral for establishing connections that are tailored to specific tenants. This feature ensures that connections can be environment-specific, such as development (Dev), quality assurance (QA), and production (Prod), while maintaining uniform connection names across these environments.

Navigate to the Manage Tenant Connections application.​

Create a new connection, giving it a meaningful name, such as demoIbhc.​

Specify the connection type, for instance, a HANA connection.​

Point this connection to the appropriate schema used in the development environment, such as UN_demo_schema_dev.​

Switch to the QA environment within the Universal Model.​

Access the Manage Tenant Connections application within QA.​

Create the same connection using the exact name as in development (demoIbhc).​

However, point this QA connection to the QA-specific schema, such as UN_demo_schema_qa.​

Within your Universal Model configurations, when setting up readers and writers, you can specify whether to use tenant-specific connections.​

Look for a checkbox labeled Use Tenant Connection.​

By selecting this checkbox, the system refers to the tenant-specific connections defined in Manage Tenant Connections rather than the global connection settings.​

Navigate to the Manage Tenant Connections application within your Universal Model.​

Initiate the process to create a new tenant-specific connection.​

Select an Existing Connection: ​

A pop-up appears, displaying a list of connections that have already been defined in the global Manage Connections settings.​

Select the connection that you intend to override for the tenant-specific configuration.​

Step 2: Choose the Schema ​

Schema Selection: ​

Once you select the connection, another pop-up displays all the schemas available to the current user ID.​

This screen lists every schema that the ID has access to.​

Choose a different schema from the list to be used for the tenant-specific connection instead of the default schema.​

For example, if the default connection points to UM_demo_schema, you can select QA_demo_schema for the QA tenant.​

Three Tiers:

• Development Tenant (Dev)
• Testing Tenant (Test or QA)
• Production Tenant (Prod)

Objective: To configure tenant-specific connections that adjust according to the schema requirements of each environment.​

Scenario: Using Tenant-Specific Connections​

Problem: You have a connection (let's call it connection1) used across Dev, Test, and Prod environments. The schema name differs in each tenant:​

• Dev Schema: dev_schema
• Test Schema: test_schema
• Prod Schema: prod_schema

Solution: By using tenant-specific connections, you can configure connection1 to point to the correct schema in each environment.