Multi-tenancy
This topic describes how to use Site Management to create and manage multiple shared spaces (tenants) on a single OpenText Enterprise Performance Engineering server.
Tip: See the Video gallery for a video on tenant administration.
Site Management overview
Site Management is the console where you run OpenText Enterprise Performance Engineering's multi-tenancy feature that enables you to create and manage multiple shared spaces (tenants) on a single OpenText Enterprise Performance Engineering server.
A tenant can be one company, or a division within one company. Each tenant's data is isolated and is not visible to other tenants. The multi-tenancy feature is useful for SaaS providers and where separation may be required between different domains and products in an organization.
Multi-tenancy is enabled automatically when more than one tenant is created. When using a multi-tenant system, the tenant UID must be passed as a query parameter in the URL in order to log on to the OpenText Enterprise Performance Engineering and Administration pages. For example:
http://localhost/admin?tenant= fa128c06-5436-413d-9cfa-9f04bb738df3
Multi-tenancy architecture
The OpenText Enterprise Performance Engineering database server stores four types of schemas: LAB, Admin, Site Management, and Project schemas. Each tenant has its own LAB and Admin database schema, and a reference in the Site Management schema for each tenant that is created.
When OpenText Enterprise Performance Engineering is installed, the Site Management schema and default LRE tenant schema are created.
If no additional tenants are created, users work with OpenText Enterprise Performance Engineering in a single-tenant environment using the default tenant.
Licenses
When using tenants in OpenText Enterprise Performance Engineering, each tenant requires its own license. The same license cannot be reused in more than one tenant, unless you split the licenses accordingly. For example, if you own a license for 5,000 Web Vusers, you can use 2,500 Vusers in Tenant A and 2,500 Vusers in Tenant B.
Note: If an existing license has already been loaded into the OpenText Enterprise Performance Engineering server, you cannot remove it and split it between tenants.
User roles
The following table describes the user roles created from Site Management.
User Roles | Description |
---|---|
Site Management Users |
Site Management users are created and used in the Site Management console only. They are a separate entity from OpenText Enterprise Performance Engineering users and cannot log onto OpenText Enterprise Performance Engineering. Note:
|
Initial Tenant Admin user |
When you create a new tenant in Site Management, you assign an administrator for managing that tenant. When the tenant is created, this user is automatically created for you in Administration with a Tenant Admin role. You need this user to log onto Administration for the first time. Note:
|
Multi-tenancy workflow
Below is an overview of the process for setting up a multi-tenancy environment.
-
Install OpenText Enterprise Performance Engineering
-
Install and configure the product. For details, see Install.
-
During the installation, enter a schema name for the Site Management database in the DB Schema Configuration page of the Configuration wizard.
-
-
Perform initial tenancy set up tasks (in Site Management)
When you install OpenText Enterprise Performance Engineering, a default tenant is automatically created. The user defined during installation is assigned as the default Site Management administrator.
-
Log onto the Site Management console as the default Site Management administrator. For details, see Log on to Site Management.
-
Create a tenant and assign an administrator for managing that tenant.
When you create a tenant in Site Management, provide credentials for the initial Tenant Admin user. This user is automatically created for you in Administration when the tenant is created, and is required to log on to Administration (for the specific tenant) for the first time. For details, see Manage tenants.
-
(Optional) Define additional Site Management users and perform other management tasks. For details, see Create and manage Site Management users, Manage tenant host resources, Check the tenant server, and Check tenant log files.
-
-
Configure lab resources for the tenant (in Administration)
Log onto Administration as a Site Admin user or as the user defined during installation, and configure the hosts and lab resources for the tenant. For details, see Host resources and lab management.
-
Define additional users to manage the tenant (in Administration) - Optional
-
Log on to Administration using the initial Tenant Admin user you assigned when creating the tenant (see step 2b above).
-
Define additional Tenant Admin users to manage the tenant as required. For details, see Define additional Tenant Admin users.
-
-
Configure test resources and create users (in Administration)
A Tenant Admin user can then log into their respective tenants in Administration and start configuring them. This includes creating and managing users, user roles and permission, and assigning projects. For details, see Manage users in a project.
Note: A Tenant Admin user has restricted access to Administration. For details, see Predefined admin roles.
-
Provide users with the tenant URL
After configuring the tenant, provide the relevant users with a tenant-specific link to the OpenText Enterprise Performance Engineering application, so that they can plan and run performance tests. For details, see Design a performance test - workflow.
Notes and limitations
The following are notes and limitations when creating and managing tenants:
Browser issues |
There is no tenant separation available when using OpenText Enterprise Performance Engineering on a Chrome browser. This means that if you have an open browser with one tenant, and you open a new browser with another tenant, you get the data from the first tenant. Solution: Use separate profiles for each tenant. |
Alerts |
Alerts are supported when using a multi-tenancy or SaaS environment. For details, see Alerts in a multi-tenant environment. |
Next steps: