Difference between revisions of "How to use Multi-Tenancy"

Latest revision as of 12:49, 12 May 2015

In the following, the administration of data from multiple clients (=tenants) with one single DLS installation is described.

This function is available only when DLS multi-tenancy has been installed. This will be asked by the installation assistant.

With multi-tenancy masks, the selection menu Tenants is available. Otherwise, it is greyed out.

When a a new object is created without selecting a tenant, an error message appears.

With multi-tenancy masks, it will make a difference whether the object is assigned to a tenant or not, that is, in the tool bar under Tenant, either the tenant’s name or <not assigned> will be displayed.

When objects are added which require a license, the tenant specific limits are checked. If a tenant is created or changed, the license dependent data are checked. The respective alarm thresholds are set tenant specific (see Section 6.3.1, "Tenants").

Basically, there is a difference between tenant dependent and tenant independent alarms.

The tenancy feature is stored in the database - but this feature is activated during setup and so it is system dependent and NOT database dependent.Hence it is possible to restore a DLS database that previously contained tenancy relations to a DLS installation where the tenancy feature is not installed.

In this rare scenario, if you have installed a system without tenant and restore a tenant database you will not see any tenants and no-tenant dependent objects afterwards since this feature was never installed before.

How to install/de-install Multi-Tenancy

First Installation

Follow the instructions of the installation assistant and, at Components, click Multi-Tenancy.

Update Installation

Follow the instructions of the installation assistant and, at Components, click Multi-Tenancy.

For all data that can be tenant specific, <not assigned> is entered as a tenant. Later, the data can be assigned to defined tenants.

Uninstalling

Execute an update installation and, at Components, deactivate Multi-Tenancy.

Import Tenants from OpenScape Voice Assistant

1) When you use a version > V3.0 of OpenScape Voice Assistant, open:

Element Manager > Element Manager Configuration > "OpenScape Voice Assistant" Tab

2) Enable Tenants synchronization and click Update Business Groups.

For each business group, a tenant and a location is created.

The names used hereby are constructed from :

Tenants and locations already existing are updated.

Set Up configuration

How to Set Up Tenants

1)Navigate to Administration > Server Configuration > Tenants.

2)Enter the required number of licenses. You can check the total number via Administration > Server Licenses.

3)If an appropriate location exists already, assign it to the tenant now via Administration > Server Configuration > Tenants > "Locations" Tab. The possible values are displayed in a selection list. It is possible to assign multiple locations. After this, continue with step 6.

4)If no appropriate location should be set up yet, click Save firstly to create the tenant, as this will be required for setting up the location. After this, navigate to Administration > Server Configuration > Location and create a location.

5)Change to Administration > Server Configuration > Location > "Tenants" Tab and assign the location to a tenant. A location can be assigned to only one tenant.

6)Change to Administration > Account Management > Account Configuration and assign the tenant to that account which shall access the data belonging to this tenant.

NOTE: The newly created tenant will be assigned to the "admin" account. This assignment cannot be effected via the GUI.

Delete Tenants

To delete a tenant, all references to this tenant must be removed first.

1)Navigate to Administration > Server Configuration > Tenants.

2)Mark the desired tenant and delete the locations listed in the "Locations" Tab.

3)Click Delete and, in the dialog window, confirm that the tenant is to be deleted.

A tenant that has been deleted will be removed automatically from the "admin" account.This cannot be effected via the GUI.

Setup a Multi-Tenancy account

1.Navigate to Administration > Account Management > Account Configuration. 2.Create an account. As Access Type, choose DLS-GUI. 3.Assign the desired roles. The role EDIT_GENERAL_ONE ensures that the account may only edit multi-tenancy masks. With the role EDIT_SYSTEM, also system relevant masks which affect all tenants can be edited. 4.Change to the "Tenants" Tab. In Tenant, enter the tenants that can be edited by this account.

Multi-tenancy accounts can edit data belonging to the assigned tenants as well as data marked with <not assigned>. To the "admin" account, the selection <all> is available in addition. With <all>, all data present in the database can be displayed and edited.

Multi-Tenancy Alarm configuration

When a tenant is set up, a tenant specific alarm configuration is created automatically. At this, the data of the generic (<not assigned>) alarm configuration are copied. If a tenant is chosen in the tool bar, the corresponding tenant dependent alarm configuration will be selected. Thus, Email addresses, batch files, and SNMP traps can be entered for license, mobility, and certificate expiration in a tenant-specific manner.

Server Assignments

For FTP server, HTTPS server, and network drives, the tenants must be assigned in the "Tenants" tab of the respective masks. The assignment of a location (see Set Up Tenants) is not sufficient, though servers are assigned to the location on its part.

Mobile Users

With regard to the mobile user functionality, please regard the following:

For the location of a tenant, an E.164 pattern should be specified in order to ensure that the call number configured for the mobile user is valid.

If call number bands are shifted from one tenant to another, the mobile users must be assigned to the new tenant manually. For this, navigate to Mobile Users > SIP Mobile User Interaction > SIP Mobile User and enter the tenant in the Tenant field.

Multi-Tenancy Profile Management

When a location is added to a tenant, also the default profiles are assigned to this tenant, including the contained templates. All remaining profiles, user data profiles, and templates can be assigned to individual tenants via the respective "Tenants" tab.

Automatic Number Pool with Multi-Tenancy

The virtual devices that are part of a Plug&Play number pool will be assigned to that location whose number pool contains the appropriate E.164 number. If Multi-Tenancy is available in this DLS installation, the E.164 number is assigned to a tenant accordingly.

@@ Line 13: / Line 13: @@
 When a a new object is created without selecting a tenant, an error message appears.
+[[File:tenant.jpg]]
 With multi-tenancy masks, it will make a difference whether the object is assigned to a tenant or not, that is, in the tool bar under '''Tenant''', either the tenant’s name or <not assigned> will be displayed.
@@ Line 46: / Line 48: @@
-:1. When you use a version > V3.0 of OpenScape Voice Assistant, open:
+:1) When you use a version > V3.0 of OpenScape Voice Assistant, open:
 :'''Element Manager > Element Manager Configuration > "OpenScape Voice Assistant" Tab'''
-:2. Enable '''Tenants synchronization''' and click '''Update Business Groups'''.
+:2) Enable '''Tenants synchronization''' and click '''Update Business Groups'''.
 :For each business group, a tenant and a location is created.
-:The names used hereby are constructed from
+:The names used hereby are constructed from :
 :<BusinessGroups Switchname (OpenScape Voice Assistant Version > V3.0) ><BusinessGroups Name>
 :Tenants and locations already existing are updated.
+== Set Up configuration==
+=== How to Set Up Tenants===
+:1)Navigate to '''Administration > Server Configuration > Tenants'''.
+:2)Enter the required number of licenses. You can check the total number via '''Administration > Server Licenses'''.
+:3)If an appropriate location exists already, assign it to the tenant now via '''Administration > Server Configuration > Tenants > "Locations" Tab'''. The possible values are displayed in a selection list. It is possible to assign multiple locations. After this, continue with step 6.
+:4)If no appropriate location should be set up yet, click '''Save''' firstly to create the tenant, as this will be required for setting up the location. After this, navigate to '''Administration > Server Configuration > Location''' and create a location.
+:5)Change to '''Administration > Server Configuration > Location > "Tenants" Tab''' and assign the location to a tenant. A location can be assigned to only one tenant.
+:6)Change to '''Administration > Account Management > Account Configuration''' and assign the tenant to that account which shall access the data belonging to this tenant.
+:'''NOTE: The newly created tenant will be assigned to the "admin" account. This assignment cannot be effected via the GUI.'''
+=== Delete Tenants===
+:To delete a tenant, all references to this tenant must be removed first.
+:1)Navigate to '''Administration > Server Configuration > Tenants'''.
+:2)Mark the desired tenant and delete the locations listed in the '''"Locations" Tab'''.
+:3)Click '''Delete''' and, in the dialog window, confirm that the tenant is to be deleted.
+A tenant that has been deleted will be removed automatically from the "admin" account.This cannot be effected via the GUI.
+=== Setup a Multi-Tenancy account===
+.Navigate to '''Administration > Account Management > Account Configuration'''.
+.Create an account. As Access Type, choose DLS-GUI.
+.Assign the desired roles. The role EDIT_GENERAL_ONE ensures that the account may only edit multi-tenancy masks. With the role EDIT_SYSTEM, also system relevant masks which affect all tenants can be edited.
+.Change to the '''"Tenants" Tab'''. In '''Tenant''', enter the tenants that can be edited by this account.
+Multi-tenancy accounts can edit data belonging to the assigned tenants as well as data marked with <not assigned>. To the "admin" account, the selection <all> is available in addition. With <all>, all data present in the database can be displayed and edited.
+=== Multi-Tenancy Alarm configuration===
+When a tenant is set up, a tenant specific alarm configuration is created automatically. At this, the data of the generic (<not assigned>) alarm configuration are copied. If a tenant is chosen in the tool bar, the corresponding tenant dependent alarm configuration will be selected. Thus, Email addresses, batch files, and SNMP traps can be entered for license, mobility, and certificate expiration in a tenant-specific manner.
+=== Server Assignments===
+:For FTP server, HTTPS server, and network drives, the tenants must be assigned in the "Tenants" tab of the respective masks. The assignment of a location (see Set Up Tenants) is not sufficient, though servers are assigned to the location on its part.
+=== Mobile Users===
+:With regard to the mobile user functionality, please regard the following:
+:*For the location of a tenant, an E.164 pattern should be specified in order to ensure that the call number configured for the mobile user is valid.
+:*If call number bands are shifted from one tenant to another, the mobile users must be assigned to the new tenant manually. For this, navigate to Mobile Users > '''SIP Mobile User Interaction > SIP Mobile User''' and enter the tenant in the '''Tenant''' field.
+=== Multi-Tenancy Profile Management===
+When a location is added to a tenant, also the default profiles are assigned to this tenant, including the contained templates. All remaining profiles, user data profiles, and templates can be assigned to individual tenants via the
+respective '''"Tenants"''' tab.
+=== Automatic Number Pool with Multi-Tenancy===
+The virtual devices that are part of a Plug&Play number pool will be assigned to that location whose number pool contains the appropriate E.164 number. If Multi-Tenancy is available in this DLS installation, the E.164 number is
+assigned to a tenant accordingly.

Views

Difference between revisions of "How to use Multi-Tenancy"

The Wiki of Unify contains information on clients and devices, communications systems and unified communications. - Unify GmbH & Co. KG is a Trademark Licensee of Siemens AG.