architecture in share point2010
TRANSCRIPT
1
Architecture Overview in SharePoint 2010
By Alexander Meijers
2
About me
• Alexander Meijers• Solution Architect / SharePoint Consultant• Over 16 years of IT experience• Small to large SharePoint projects• Owner of the Dutch SharePoint User Group• SharePoint Black belts group• SharePoint Geek and Speaker
• Blog: http://www.bloggix.com• Usergroup: http://www.dutchsug.nl• Twitter: @ameijers
3
Agenda
• Hardware requirements• Topologies• Services & terminology• Service deployment• Multitenancy
Many demos!!
4
HARDWARE REQUIREMENTS
5
Hardware requirements
• 64 bit, dual processor, 3GHz• 8 GB RAM• Minimal 100 GB disk space• DVD Drive• Network / Internet Connectivity
These hardware requirements are for both WFE and Database servers.
6
Database Server requirements
• 64 bit environment• Windows Server 2008 Enterprise + Service Pack 2• SQL Server 2005 Service Pack 3 + Cumulative
Update 3• SQL Server 2008 Service Pack 1 + Cumulative
Update 2• Pre-requisites
– SQL Server 2008 Native Client– Microsoft SQL Server 2008 Analysis Services
ADOMD.NET– ADO.NET Data Services v1.5 CTP2
7
TOPOLOGIES
8
Topologies
• Limited deployment – One-server farm– For evaluation purposes or less then 100 users– All roles on one server– Same server used for SQL Server
• Limited deployment – Two-tier farm– Up to 10.000 users– Single WFE Server (Web server + all application server
roles)– Single Database Server– Only in secure segment
9
Topologies
• Small farm – Two-tier farm– Two web servers for 10000 to 20000 users– Both web servers has Query server role and one has all other
application roles– Single Database Server
• Small farm – Three-tier small farm– Same as two-tier farm– Separate application server for other application roles
• Small farm – Three-tier small farm optimized for search– Same as three-tier farm– Separate search databases
10
Topologies
• Medium farm– Scaled for search to serve up to 40 million items– 2 or more web servers depending on number of users required to
serve– 2 application servers for query and crawl server– All other server roles installed on separate application server. – At least 2 database servers for search databases– At least one or more servers for other databases
• Large farm– Use of web servers, application servers and database servers– Group services or databases with similar performance characteristics
on dedicated servers– Use dedicated server group for Excel Calculation or Search
11
SERVICES & TERMINOLOGY
12
Services Infrastructure
• Services are not part of a SSP anymore• Part of SharePoint Foundation 2010• Each service can be configured
independently• Create your own services
13
Terms
• Service– Parts installed on a farm that provide some functionality to your
environment
• Service Applications– A configurable running physical instance of a service
• Service Instance– Instance of the running service on an Application Server
• Application proxy– A service proxy (virtual entity) connects a service application to web
applications.
• Service Consumer– A piece of SharePoint (e.g. Web Part) which makes the functionality of
the service available to users
14
Service application
It is a configurable running physical instance of a service.
• Provides data or computing resources• Exposes an administrative interface• Uses resources due to service database
and application pool• Deploy multiple instances of the same
service in a farm
15
Application Proxy
A service proxy (virtual entity) connects a service application to web applications.
• The proxy is created when the service application is created
• Some of these connections include settings (e.g. Metadata service)
16
Application Proxy Groups
A group of application proxies
• All application proxies are included in a default group by default
• Create your own custom group– Not reusable across multiple web applications
17
Demo
18
SERVICE DEPLOYMENT
19
Deploy and use services
• Deploy only the service you want to the farm
• Configure per Web Application which services to use
• Some services can be shared across different farms (called cross-farm services)
• Share services across multiple Web Applications within the same farm
• Some services can be shared only within a single farm
20
Ways of deploying services
• Select services while running the initial configuration wizard
• Adding services via the Manage Service Applications page
• Windows PowerShell
21
Service Topologies
• Single Farm– Single Service Application– Multiple Service Application
• Service Application Farm• Content-only Farm consuming from
Service Application Farm• Multiple Farms
– Mixed Service Application
22
Demo
23
MULTITENANCY
24
Multitenancy
The ability to partition data of services or software in order to accommodate multiple tenants
• Multitenancy of services• Mostly deployed and managed through
PowerShell• Isolation of data per tenant or shared across all
tenants• Tied to site subscriptions
25
Data isolation
• Service installed in partitioned or un-partitioned mode
• Not possible to change after installation
• Some services which do not store tenant data do not need to be partitioned (e.g. PowerPoint, Access service, …)
• FAST Search Server 2010 for SharePoint cannot be partitioned
Partition B
Partition A
Data
26
Tenant data or not?
27
Site subscriptionsA logical group of site collections which share settings, features (packs) and data from services
• Uses a subscription ID to map to tenants
• Site collections must reside on the same farm but can be spread across multiple web applications
• Subscription Settings service• Tenant administrators manage
their own site collections through a Tenant Administration Site
• One instance of the service application shared across multiple tenants
28
Feature packs
Sets of features activated by the Farm Administrator for tenants to activate and use
• Can be a mixture of web and site features• Sites in the subscription can only use the features
specified in the pack.• Applied through Windows PowerShell• Custom feature sets possible• Site templates which are depending on non
available features are not shown to the tenant
29
PowerShell
• Stop using “stsadm” commands and start with PowerShell!
• Multi-tenancy is done through PowerShell– Enabling– Site Subscriptions– Feature Packs
30
PowerShell – Setup Multi-tenancy
• Enable multi-tenancy through a service– New-SPSubscriptionSettingsServiceApplication– New-SPSubscriptionSettingsServiceApplicationProxy
• Create Service Applications with option –PartitionMode– New-SPMetadataServiceApplication– New-SPMetadataServiceApplicationProxy
• Create an Site Subscription id– New-SPSiteSubscription
• Create an tenant administration site– New-SPSite with option -Template tenantadmin#0– AdministrationSiteType to TenantAdministration
• Add a site collection and the tenant administration site to the Site Subscription– Via tenant administration site– Using New-SPSite with option -SiteSubscription
31
PowerShell – Setup Feature Packs
• Create a Site Subscription Feature Pack– New-SPSiteSubscriptionFeaturePack
• Add features to the Feature Pack• Add-SPSiteSubscriptionFeaturePackMember
• Find out your Site Subscription id• Use the Site Subscription Settings Manager to assign the
Feature Pack to the Site Subscription– [Microsoft.SharePoint.SPSiteSubscriptionSettingsManager]::Local– AssignFeaturePackToSiteSubscription
• Remove association– Use the Site Subscription Settings Manager to assign $Null to the Site
Subscription
32
Demo
33
Multitenancy environments
• Enterprise hosting – Some data is shared across the organization
like People Service, Search Service and others
• Shared hosting– Data is isolated between the different tenants
(customer sites)
34
Questions?