Deploy a separate search farm when above 40 million itemsDepending on performance add more application servers to divide server roles
Service applications can be deployed to different application pools to achieve process isolation. However, farm performance is optimized if services are contained within one application pool.
Some connections might include settings that can be modified. For example, if a Web application is connected to multiple instances of the Managed Metadata service, you must indicate which of the connections is connected to the primary service application which hosts the corporate taxonomy.
Multitenancy refers to a principle in software architecture where a single instance of the software runs on a server, serving multiple client organizations (tenants). Multitenancy is contrasted with a multi-instance architecture where separate software instances (or hardware systems) are set up for different client organizations. With a multitenant architecture, a software application is designed to virtually partition its data and configuration so that each client organization works with a customized virtual application instanceFor partitioned mode both service and service connection must be deployed in partitioned modeRecommendation: Deploy all services as partitioned to ensure that reporting and diagnostic information is reported correctly.
Tenant administration is provided through a site template titled "Tenant Administration," which is associated with a subscription ID. This site template is hidden and the site can be created and given to tenant administrators only by a farm administrator. A tenant administration site is deployed as a separate site collection. Multi tenant admin sites: these sites give you a central location where all of the sites for a particular tenant can be managed. It includes things like managing certain aspects of service applications (like user profiles, managed metadata store, etc.). It also allows you to view all of the site collections in the tenancy, create new site collections, manage the owners of those site collections, etc.Multi tenant member sites: tenancy in SharePoint 2010 is managed through something we call a subscription. Simply stated, a subscription is just a GUID that we can use to identifiy members of a subscription as well as data associated with a subscriber. The membership identity is how we can determine which site collections are part of which tenancy. From a data perspective, we can use that subscriber key when data is stored in a service application. For example, so tenant A can have a set of administrators and data in the managed metadata service application, and tenant B can have an entirely different set of admins and data. From a farm perspective in this scenario, you are only using one instance of the managed metadata service application, but it is being shared by all tenants. However their data is isolated and secured from one another by virtue of their subscriber ID.Feature Packs: feature packs are ways in which SharePoint features, the same regular features you know and love, can be organized into groups (NOTE: "feature packs" is what this has been called, it may be called something else by the time the product ships). Once you organize these features into feature packs, you can associate them with a subscriber. Once that's been done, that subscriber can only use those features that have been added to the feature pack. That gives you control over which tenants are using which features, as well as giving you a means by which you can create different packaged offerings at different prices for hosting customers.
If third-party features are added to a farm, the use of these features with feature sets should be tested to ensure that these do not add additional feature activation dependencies that are not honored within the feature set.
Architecture In Share Point2010
Architecture Overview in SharePoint 2010<br />By Alexander Meijers<br />1<br />
About me<br />Alexander Meijers<br />Solution Architect / SharePoint Consultant<br />Over 16 years of IT experience<br />Small to large SharePoint projects<br />Owner of the Dutch SharePoint User Group<br />SharePoint Black belts group<br />SharePoint Geek and Speaker<br />Blog: http://www.bloggix.com<br />Usergroup: http://www.dutchsug.nl<br />Twitter: @ameijers<br />2<br />
Hardware requirements<br />64 bit, dual processor, 3GHz<br />8 GB RAM<br />Minimal 100 GB disk space<br />DVD Drive<br />Network / Internet Connectivity<br />These hardware requirements are for both WFE and Database servers.<br />5<br />
Database Server requirements<br />64 bit environment<br />Windows Server 2008 Enterprise + Service Pack 2<br />SQL Server 2005 Service Pack 3 + Cumulative Update 3<br />SQL Server 2008 Service Pack 1 + Cumulative Update 2<br />Pre-requisites<br />SQL Server 2008 Native Client<br />Microsoft SQL Server 2008 Analysis Services ADOMD.NET<br />ADO.NET Data Services v1.5 CTP2<br />6<br />
Topologies<br />Limited deployment – One-server farm<br />For evaluation purposes or less then 100 users<br />All roles on one server<br />Same server used for SQL Server<br />Limited deployment – Two-tier farm<br />Up to 10.000 users<br />Single WFE Server (Web server + all application server roles)<br />Single Database Server<br />Only in secure segment<br />8<br />
Topologies<br />Small farm – Two-tier farm<br />Two web servers for 10000 to 20000 users<br />Both web servers has Query server role and one has all other application roles<br />Single Database Server<br />Small farm – Three-tier small farm<br />Same as two-tier farm<br />Separate application server for other application roles<br />Small farm – Three-tier small farm optimized for search<br />Same as three-tier farm<br />Separate search databases<br />9<br />
Topologies<br />Medium farm<br />Scaled for search to serve up to 40 million items<br />2 or more web servers depending on number of users required to serve<br />2 application servers for query and crawl server<br />All other server roles installed on separate application server. <br />At least 2 database servers for search databases<br />At least one or more servers for other databases<br />Large farm<br />Use of web servers, application servers and database servers<br />Group services or databases with similar performance characteristics on dedicated servers<br />Use dedicated server group for Excel Calculation or Search<br />10<br />
Services Infrastructure<br />Services are not part of a SSP anymore<br />Part of SharePoint Foundation 2010<br />Each service can be configured independently<br />Create your own services<br />12<br />
Terms<br />Service<br />Parts installed on a farm that provide some functionality to your environment<br />Service Applications<br />Aconfigurable running physical instance of a service <br />Service Instance<br />Instance of the running service on an Application Server<br />Application proxy<br />A service proxy (virtual entity) connects a service application to web applications.<br />Service Consumer<br />A piece of SharePoint (e.g. Web Part) which makes the functionality of the service available to users<br />13<br />
Service application<br />It is a configurable running physical instance of a service.<br />Provides data or computing resources<br />Exposes an administrative interface<br />Uses resources due to service database and application pool<br />Deploy multiple instances of the same service in a farm<br />14<br />
Application Proxy<br />A service proxy (virtual entity) connects a service application to web applications.<br />The proxy is created when the service application is created<br />Some of these connections include settings (e.g. Metadata service)<br />15<br />
Application Proxy Groups <br />A group of application proxies<br />All application proxies are included in a default group by default<br />Create your own custom group<br />Not reusable across multiple web applications<br />16<br />
Deploy and use services<br />Deploy only the service you want to the farm<br />Configure per Web Application which services to use<br />Some services can be shared across different farms (called cross-farm services)<br />Share services across multiple Web Applications within the same farm<br />Some services can be shared only within a single farm<br />19<br />
Ways of deploying services<br />Select services while running the initial configuration wizard<br />Adding services via the Manage Service Applications page<br />Windows PowerShell<br />20<br />
Service Topologies<br />Single Farm<br />Single Service Application<br />Multiple Service Application<br />Service Application Farm<br />Content-only Farm consuming from Service Application Farm<br />Multiple Farms<br />Mixed Service Application<br />21<br />
Multitenancy<br />The ability to partition data of services or software in order to accommodate multiple tenants<br />Multitenancy of services<br />Mostly deployed and managed through PowerShell<br />Isolation of data per tenant or shared across all tenants<br />Tied to site subscriptions<br />24<br />
Data isolation<br />Service installed in partitioned or un-partitioned mode<br />Not possible to change after installation<br />Some services which do not store tenant data do not need to be partitioned (e.g. PowerPoint, Access service, …)<br />FAST Search Server 2010 for SharePoint cannot be partitioned<br />25<br />Data<br />Partition A<br />Partition B<br />
Site subscriptions<br />A logical group of site collections which share settings, features (packs) and data from services<br />27<br />Uses a subscription ID to map to tenants<br />Site collections must reside on the same farm but can be spread across multiple web applications<br />Subscription Settings service<br />Tenant administrators manage their own site collections through a Tenant Administration Site<br />One instance of the service application shared across multiple tenants<br />
Feature packs<br />Sets of features activated by the Farm Administrator for tenants to activate and use<br />Can be a mixture of web and site features<br />Sites in the subscription can only use the features specified in the pack.<br />Applied through Windows PowerShell<br />Custom feature sets possible<br />Site templates which are depending on non available features are not shown to the tenant<br />28<br />
PowerShell<br />Stop using “stsadm” commands and start with PowerShell! <br />Multi-tenancy is done through PowerShell<br />Enabling<br />Site Subscriptions<br />Feature Packs<br />29<br />
PowerShell – Setup Multi-tenancy<br />Enable multi-tenancy through a service<br />New-SPSubscriptionSettingsServiceApplication<br />New-SPSubscriptionSettingsServiceApplicationProxy<br />Create Service Applications with option –PartitionMode<br />New-SPMetadataServiceApplication<br />New-SPMetadataServiceApplicationProxy<br />Create an Site Subscription id<br />New-SPSiteSubscription<br />Create an tenant administration site<br />New-SPSitewith option -Template tenantadmin#0<br />AdministrationSiteType to TenantAdministration<br />Add a site collection and the tenant administration site to the Site Subscription<br />Via tenant administration site<br />Using New-SPSitewith option -SiteSubscription<br />30<br />
PowerShell – Setup Feature Packs<br />Create a Site Subscription Feature Pack<br />New-SPSiteSubscriptionFeaturePack<br />Add features to the Feature Pack<br />Add-SPSiteSubscriptionFeaturePackMember<br />Find out your Site Subscription id<br />Use the Site Subscription Settings Manager to assign the Feature Pack to the Site Subscription<br />[Microsoft.SharePoint.SPSiteSubscriptionSettingsManager]::Local<br />AssignFeaturePackToSiteSubscription<br />Remove association<br />Use the Site Subscription Settings Manager to assign $Null to the Site Subscription<br />31<br />
Multitenancy environments<br />Enterprise hosting <br />Some data is shared across the organization like People Service, Search Service and others<br />Shared hosting<br />Data is isolated between the different tenants (customer sites)<br />33<br />