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.

Jump to: navigation, search
(Install/Deinstall Multi-Tenancy)
Line 20: Line 20:
  
 
'''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.'''
 
'''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.'''
 
 
== 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
 
<BusinessGroups Switchname (OpenScape Voice Assistant Version > V3.0) ><BusinessGroups Name>. Tenants
 
and locations already existing are updated.
 

Revision as of 10:32, 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.