About SharePoint 2013 Multi-tenancy (i)

About multi-tenancy (multi-tenancy)

What I'm going to introduce to you here is the multi-tenancy concept in SharePoint 2013, what is multi-tenancy? What is the meaning and use of the multi-tenancy model? I am here to uncover this mysterious veil for all of you.

Multi-tenancy: refers to the ability to manage and partition the site data and the shared services or software to accommodate multiple tenants. This is relative to running multiple instances of the service or setting up separate hardware. In Microsoft products and technologies, service multi-tenancy creates a managed environment that maximizes farm resources. Before you know the managed environment, you must understand the service architecture.

Novice SharePoint Engineers rarely encounter scenarios where multi-tenancy is used, mainly because multi-tenancy is primarily used for software development of e-commerce platform classes. SharePoint is often used by organizations within the enterprise, so many development engineers know little about it.

One, enabling multi-tenancy of key components and services

Web Application , which is made up of an IIS Web site. This web site acts as a logical unit and a security unit for the site collection that you create. Each Web application consists of a different IIS Web site that uses a unique or shared application pool.

host-named site Collections , which enable you to assign unique DNS names to a site collection. For example, you can call it a http://a.contoso.com or http://b.contoso.com. This allows you to deploy many sites that use unique DNS names in the same Web application. Of course, a Web application can also contain many path-based site collections that share the same host name (DNS name). For example, http://a.contoso.com/sites/site1 or Http://a.contoso.com/sites/site2

fundamentally, host-named site collections are the only way to extend a multitenant environment. and provides the maximum flexibility for the URL namespaces used. If you use path-based sites in conjunction with multi-tenancy, the software boundaries used to manage the paths will soon be reached.

For additional information about how to plan host-named site collections for SharePoint 2013, see Architecture and deployment of host-named site collections (SharePoint 2013).

Service Group (Agent Group), which is a set of service applications that are selected for use in Web applications. By default, all service applications are included in the default group unless another group is specified when the service application is created. You can add or remove service applications at any time in the default group. When you create a Web application, you can select a service group or select only a few service applications to create a custom service group. A custom server group cannot be reused across multiple Web applications.

Service proxy , which creates a proxy for the service application when the service application is created. A proxy is a virtual entity that connects a Web application to a service application. If you use PowerShell to create a service application, you need to manually use PowerShell to create the service proxy.

A Service Application is a logical representation of the specified service and its security and management configuration. Different service applications are implemented in different ways, which affects the design of multi-tenant solutions. To determine the list of service applications available in SharePoint 2013 and their availability between SharePoint versions with Multitenant features, see Services and features in general guidance for host providers in SharePoint Server 2013 Part.

feature packs and licenses are a way to limit the functionality of a Web site or web to grouping together. When SharePoint features are grouped, they can be associated with a site subscription (that is, a tenant). All site collections in this site subscription (tenant) can only use features that are scoped to the site or Web by the Feature Pack.

In SharePoint 2013, add a new feature to assign each user a different SharePoint license. It also enables run-time SharePoint license checking. This feature provides service providers with greater flexibility to build different service offerings in a simplified deployment model.

Information Management Management , SharePoint2013 adds support for multi-tenancy to manage tenant-level Information Rights Management settings.

Ii. how multi-tenancy works in SharePoint 2013

Native multi-tenancy has been introduced in SharePoint Server 2010 to publish SharePoint as an effective platform for multi-tenancy. SharePoint Server 2013 inherits the same features and designs associated with multi-tenancy, and adds new features to support multi-tenant deployments.

In SharePoint Server 2010, a new shared services model was implemented. This new model is called a "service application." These service application architectures allow one set of services to be associated with a set of Web applications, and another set of services associated with another group of Web applications. In addition, you can configure the same service application for different WEB application groups, but the settings differ. A Web site can be configured to use only the services you need, not the entire service family.

In SharePoint, multi-tenancy refers to the ability to partition the data of a shared service to accommodate multiple tenants. This is in contrast to installing separate dedicated hardware, or even multiple dedicated instances running the specified service.

Services can be configured to share data across all tenants or to partition data for each tenant, for example, to provide data isolation. Each service can be set differently. You can use Windows PowerShell to create services in partitioned mode, or you can use Windows PowerShell or central Administration to create services in non-partitioned mode. After it is created, you cannot change the mode of the service. to implement partitioning, both service and service connections must be deployed in partitioned mode. A service connection is called a proxy in Windows PowerShell.

Not all services can be partitioned. Services that do not store tenant data, such as PowerPoint Automation services, do not require partitioning. These services can be shared among multiple tenants without leaking tenant-specific data.

Shows how to partition the service data:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/54/7C/wKioL1SEYrbDVE3rAABFAkRhHcs049.jpg "title=" Ic739303.jpg "alt=" Wkiol1seyrbdve3raabfakrhhcs049.jpg "/>

In SharePoint, multi-tenancy is bound to a site subscription. A site subscription is a logical group of site collections that can share settings, features, and service data. Each tenant's site collection is lumped together using the subscription ID. The subscription ID is used to map features, services, and sites to tenants, and to partition service data based on tenants. The Subscription Settings service tracks multi-tenancy services and subscription IDs.

Here's how it works:

1. 1. The farm administrator deploys the service to the server farm, which includes the Subscription Settings service. Service applications can be deployed in partitioned mode when their data is detached from each other, or in non-partitioned mode when the data is shared across all tenants. Some services do not store tenant data and are shared across all tenants without partitioning.

   2. Farm administrators use Windows PowerShell to deploy tenant administration sites for each tenant. The tenant Administrator site is associated with the subscription ID. Administrators can deploy additional site collections for each tenant. Each site collection is bound to the tenant's subscription ID.

   3. All service applications that are connected at the Web application level are available for use by site collections within the Web application. The administrator selects the services to be provided and becomes the active administrator for each tenant. The tenant's subscription ID is used to map the service to the site collection.

   4. Tenant administrators use the assigned Tenant Administration site to manage their own site collections.

   5. Site collections for multiple site subscriptions can be hosted in a single Web application.

   6. Multiple site subscriptions can share a content database, or a site subscription can contain content between multiple content databases.

   7. All site collections for a single site subscription must be in the same farm, but they can be extended between WEB applications.

Farm administrators can host multiple tenants on the same farm and centrally manage the deployment of services and features. Tenant administrators can manage the configuration of features delegated by administrators and control the functionality of the site.

SharePoint coordinates its management capabilities with regular managed roles, as shown in the following table.

Role	Administrator type	Description
Service Provider Administrator	Server farm Administrator	Manage farm-level settings and hardware. Control database configuration. Installs all new features and solutions that are approved. Branding can be established on the Tenant Management page.
Managed Company Admins	Tenant Administrator	Purchase space, functionality, and bandwidth from your service provider. Control the architecture of the customer site rather than the content. Configure tenant settings. Check usage statistics.
Hosting company	site Administrator	Owns the site collection. Configure the Site settings for features and services that will be exposed. Check usage statistics.

Tenant management is provided through the Tenant Administration site, based on a site template titled "Tenant Management." Tenant administrators can use Windows PowerShell cmdlets to create a tenant administration site and grant access to tenant administrators. Displays the home page of the tenant administration site.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/54/7E/wKiom1SEY1Syrzp7AADwsbg1ySQ737.jpg "title=" Ic739304.jpg "alt=" Wkiom1sey1syrzp7aadwsbg1ysq737.jpg "/>

Tenant administrators can use the Tenant administration site to manage multiple aspects of a subscription. For example, a tenant administrator can manage all site collections for a subscription from a single location. Displays the site Collection Administration page for the tenant administration site.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/54/7C/wKioL1SEZBKDM1i4AAD9XhiUtYk502.jpg "title=" Ic739305.jpg "alt=" Wkiol1sezbkdm1i4aad9xhiutyk502.jpg "/>

This article is from the "Net Life" blog, make sure to keep this source http://642197992.blog.51cto.com/319331/1587369

About SharePoint 2013 Multi-tenancy (i)