Cisco Acano X-series
Cisco Meeting Server Release 2.0+ : Multi-tenancy considerations
4
1 Introduction
In this document, the term “coSpace has been replaced with “space”.
The Cisco Meeting Server supports multi-tenancy; this refers to sub-dividing the capacity of the
server into a set of “islands”, where each island has all of the functionality of the unit as a whole,
but has no access to the resources (for instance users, spaces, or active calls) of other tenants.
For example, if users that are associated with a tenant search for a space, they only see spaces
associated with their own tenant.
server into a set of “islands”, where each island has all of the functionality of the unit as a whole,
but has no access to the resources (for instance users, spaces, or active calls) of other tenants.
For example, if users that are associated with a tenant search for a space, they only see spaces
associated with their own tenant.
The multi-tenancy provision is through the Cisco Meeting Server API. (For details of features
that support multi-tenancy, see the Cisco Meeting Server API Reference Guide.)
that support multi-tenancy, see the Cisco Meeting Server API Reference Guide.)
This document describes setting up multi-tenancy usage.
Note: When using multi-tenancy, not every user or space (and therefore not every call) has to be
associated with a tenant.
associated with a tenant.
1.1 How to use this Document
This document is part of the documentation set (shown in Figure 1) for the Cisco Meeting
Server.
Server.
1 Introduction