Download - SharePoint 2010 Global Deployment
Help! My Users Are Everywhere: Designing for a Global SharePointJoel OlesonSr. Architect & EvangelistQuest Softwarehttp://www.sharepointjoel.com@joeloleson
SESSION CODE: OSP312
Objectives And Takeaways
Understand Key Design DecisionsTradeoffs of Central vs. Regional/DistributedSharePoint 2010 Global Service Deployment ConsiderationsGlobal Considerations with Third Party Solutions
Agenda
What’s Changed…Drill Down into Service Apps – Global vs. LocalDistributed Multi Farm Service DeploymentsCentralized DeploymentsRegional DeploymentsGlobal Search Architecture Considerations
The SharePoint 2010 Global Story in a Nutshell…
Geo DilemmaTo distribute or not distribute THAT is the question!
Cost vs. Usability vs. ManageabilityBandwidth can be bought but latency is bound to laws of physicsDifferent stakeholders -> different priorities/preferences
IT tends to favor Centralized (low cost)Business just wants it to work (faster the better)
The SP2010 Global Story - What’s Really Changed?The SSP exploded into Service Applications and Proxy GroupsSearch has changed Dramatically
Index Redundancy Distributed Partitioning supporting many crawlersProperty & Crawl databases – All crawled content is in the databases
Groove -> SharePoint WorkspaceBetter Offline & WAN Online StoryDifferencingLicensing
Mirroring Aware – More of DR story…Replication – Sorry!Pages have been optimized
Comparing SharePoint Capacity Guidelines
SharePoint Capacity PlanningSharePoint 2007 SharePoint 2010
Items per List view 2000 5000
Docs per Library 5 Million 10 Million
DB Sizing 100 GB 200 GB
Doc Editors 1 99 Max
Content Db per Web App 100 300
Indexed Items 50 Million 100 Per Search Application
Site Collections per Web App 50,000 500,000
Drill Down into Global Aspects of Service Apps
Local Only Service Apps "Foundation"
Service Applications
Application Registry State
Usage and Health
Collection
Web Analytics
Local Only Service Apps "Standard"
Service Applications
Word Auto Conversion
Word Viewing
Office Web Apps
Lotus Notes Connector
Web App Clients
Local Only Service Apps "Enterprise"
Service ApplicationsLOCAL ONLY
Access Services Excel Services Visio Services PerformancePoint
Service App AssociationsWeb App
Service Application
Group
Service App Connection (For
Publishing)
Service App
Services on Server
Service App DB
WAN Friendly Service Apps HTTPS WCF + XML
Glo
bally
Con
sum
able
Business Connectivity*
Managed Metadata Service
Search
User Profiles
Secure Store(Single Sign-On)
Web Analytics*
Shared
*SharePoint Foundation
Manage Service Application
Managing and Publishing Service Apps
Demo
Databases
Export Certificates to Configure TrustProvider
Export root certificate by running the following cmdlets : $rootCert = (Get-SPCertificateAuthority).RootCertificate $rootCert.Export("Cert") | Set-Content "C:\PublisherFarmRoot.cer" -Encoding byte
Consumer:Export root certificate by running the following cmdlets: $rootCert = (Get-SPCertificateAuthority).RootCertificate $rootCert.Export("Cert") | Set-Content "C:\ConsumerFarmRoot.cer" -Encoding byte
Consumer: Export Security Token Service (STS) certificate by running the following cmdlets: $stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate $stsCert.Export("Cert") | Set-Content "C:\ConsumerFarmSTS.cer" -Encoding byte
Copy above certificates from Publisher to Consumer and vice versa.
Import Certificates to Configure TrustProvider
Import root certificate from consumer farm and create a Trusted Root Authority by running the following cmdlets: $trustCert = Get-PfxCertificate “%[File Path]%\ConsumerFarmRoot.cer" New-SPTrustedRootAuthority "ConsumerFarm" -Certificate $trustCertImport STS certificated from consumer farm and create a Trusted Service Tokern Issuer by running the following cmdlets: $stsCert = Get-PfxCertificate "c:\ConsumerFarmSTS.cer" New-SPTrustedServiceTokenIssuer "ConsumerFarm" -Certificate $STSCert
Verify TrustGo to Central Admin select “Security” and click on “Manage trust” link and make sure that the certificates are imported successfully
Centralized Deployments
Weighing the Global Considerations
Central Regional
Single Central Services Farm – Most Common
Web Applications: Enterprise Portal/Search, CRM, Departments, My Sites, Team Sites
Global Services:Secure StoreBusiness Data ConnectivityManaged Metadata (Primary)Web AnalyticsProfilesSearch
Local Only Service Applications:Usage & Health Data CollectionLotus Notes ConnectorVisio GraphicsExcel ServicesPerformancePoint
Central Farm
Multi Farm
Web Application: My Site Hub
Global Services Provided:User ProfilesWeb Analytics
Services Consumed:SearchManaged Metadata
Local Only Service Applications:Usage & Health Data CollectionWeb Application ClientsSocial Tagging
My Site & Team Collab Farm
Web Applications: Enterprise Portal/Search, CRM, Departments
Global Services Provided:Secure StoreBusiness Data ConnectivityManaged MetadataWeb AnalyticsSearch
Services Consumed:Profiles
Local Only Service Applications:Usage & Health Data CollectionLotus Notes ConnectorVisio GraphicsExcel ServicesPerformancePoint
Intranet Portal, Search & ECM Farm
4
Search Farm
Centralized Deployment
Central Solution
Central Deployment +Partner Solution: WAN/Network Acceleration
REDMOND
WAN Accelerator Datacenter
All Services in one Central Farm
Central Search
Central Directory
WAN Accelerator remote office
BEIJING
10s-100s of Local WAN Accelerators
~5x - 1st Request
~43x - 2nd Request
Central SolutionEasiest to maintain and operate.Cheapest SolutionEasiest to support
Is it the Utopia or just for IT? - Don’t forget D/R!!!
Key Network Considerations
Latency - #1Bandwidth #2Utilization (is it already high % consumed?)Expected usage (page and file size, and common usage patterns)
Other Network Considerations (Customer Case Study)
Politics (AD trusts/Affiliates) DeloitteBusiness Requirements (Speed comfort) EnergizerNetwork Map (Microsoft)Network Roadmap & Data center Consolidation Goals (HP)
Regional/Distributed Deployments
Regional DeploymentOptimized for Latency
New York HQLONDON Tokyo
Regional Scope ServicesLocal My Site Hub
Regional Portal
Consumes Search & Profiles
Sychnronizes Metadata Termstore
Enterprise Scope Services
Enterprise Search
Enterprise Profiles
Enterprise Managed Metadata Termstore
Regional Scope ServicesLocal My Site Hub
Regional Portal
Consumes Search & Profiles
Sychnronizes Metadata Termstore
Regional Example
Service Apps RO
• Consumes
• Managed Metadata (Secondary)
• Excel Services• Usage & Health
Service Apps HQ
• Search• Profiles• Business
Connectivity• Managed Metadata
(Primary)• Web Analytics• Usage & Health
Service Apps RO
• Consumes
• Managed Metadata (Secondary)
• Visio• Usage & Health
Web Application: Team, Portals, My Site Hub
Global Services Provided:Metadata Management (secondary)Web Analytics
Services Consumed:SearchManaged MetadataProfiles
Local Only Service Applications:Usage & Health Data CollectionWeb Application Clients
Regional Farm
Web Applications: Enterprise Portal/Search, Departmental ECM, My Sites, Team SitesGlobal Services Provided:Secure StoreBusiness Data ConnectivityManaged Metadata (Primary)Web AnalyticsProfilesSearchServices Consumed:Managed Metadata & Web Analytics
Local Only Service Applications:Usage & Health Data CollectionLotus Notes ConnectorVisio GraphicsExcel ServicesPerformancePoint
Central Farm
Determining Latency and Page and File Elements
demo
Global Search Considerations
Global Scale SearchCentralized vs. Distributed farms
Crawling across the wire vs.
Querying across the wirePartitioning data
Based on Geography vs. ContentFederating results
Merging results from different indexes loses relevancy
N
S
EW
Data centers Sites0-100ms 101-200ms 201-300ms >300msbackbone
Munich
Peking
Chicago
35MB
50 MB
50MB
2MB
2MB
2MB
1 MB
Options for Enteprise Search with Regional DeploymentCrawling regional farms from the central farmUsing search federation across farms with local crawling
Note: If SharePoint Foundation is used within a region, search is scoped to the Site Collection level
WAN Optimization
End-to-End Perceived Network Performance
Client Performance:CPU/Processor DelayVirtual/Physical Memory LimitsNIC Config, Network Drivers and TCP/IP ConfigClient Application VersionsProxy Config
Client LANSwitch ConfigUtilization
WAN:Link Speed(Bandwidth)Delay (Latency)Packet Loss, Retransmissions, TimeoutsNetwork ThroughputRound Trips
Server LAN Performance:Switch ConfigContention for Uplink
Server Performance:CPU/Processor DelayVirtual and Physical Memory LimitsNIC/Network Drivers and TCP/IP configNetwork Speed (10/100/1000MB)Server Software Layer
End to End Examples
Intranet RecommendationsCentralized Deployments Regional Deployments/Regional
Access to Central HubBandwidth: ranges of 3Mbps for Larger offices and T3/ E3
Latency: No greater ~150 milliseconds for large offices
Utilization: Segments should not be sustained at more than 30%
Page load time: Target of less than 5 seconds
Bandwidth: Ranges of 1.5Mbps (T1/E1) and above
Latency: No greater than 100 msecs for connected offices with 5 or more information workers
Utilization: Sustained should not be more than 35%
Page Load time: Target of less than 10 seconds
Page and File Optimizing for the WAN
Page optimization techniquesUse BLOB cacheUse IIS Compression for dynamic pagesMinimize images sizes and countDelay downloading of core.jsOptimize list view pages (allitems.aspx)Use Fiddler2 to troubleshoot page assets (http://www.fiddlertool.com)
Index OptimizationSpecialize crawl time schedules for WAN links
Increase time-out settings for searchCrawler impact rules/ # crawl threads
Dev Techniques for the WAN
Optimizing Web Parts for the WANRe-use built-in Styles vs. Creating Custom StylesStoring State
Use Server Cache classWeb.config: enableViewState=trueUse Control State
Page.RegisterRequiresControlState()LoadControlState(), SaveControlState()
Maximize perf on Webparts displaying dataUse inline XML data islandsUse Client-Side scripts to connect to WebservicesAJAX and JSON is lightweight
Cache Config Levels
Web App – Disk based caching in web.configSite collection – configure output cache and object cache settingsSite – output cache settingsPage layout – output cacheWeb Part – settings in dwp code Query – i.e. RSS Feed cache is 5 min by default, verify query webpart is cached
Cache
Cache Type Level What for?
Output caching and cache profiles Individual page level Pages - Ideal for heavily accessed Web sites that do not need to present new content frequently.
Object caching Individual Web Part control, field control, and content level
Heavy Queries and Navigation - Including cross-list query caching
Disk-based caching for Binary Large Objects (BLOBs)
Individual BLOB level and caches images, sound, movies, and code
Page Elements - Supports .gif, .jpg, .js, .css, and other images, sound, and objects that are stored as binary large objects
Third Party Global Deployment Considerations
Sampling of Global Optimization Solutions & PartnersWAN Accelerators
CiscoCitrixCerteonPacketeerRiverbedF5
Cache Devices/Network OptimizationCiscoF5InktomiISA and IAG Server
Offline Client SolutionsGroove & SharePoint WorkspaceColligo
Data ReplicationSyntergyWinApp TechnologiesAvePointInfonic
Multi-farm managementQuest SoftwareEchoTechnologiesIDevFactoryAvePointCorasWorksCommVaultSymantec
Byte Level ReplicationNeverfailDouble-take
SAN ReplicationHPEMC CenteraHitachi Data Systems
Page OptimizationAptimizeNcache
Sample Test Data…
Page Load Times – Common User OperationConcurrency:
Bandwidth (Mbps)50 100 500 1000 10,000 Utilization
(%)Throughput
(Kbps)45 (T3), Latency = 50ms 1.17 1.17 1.18 1.20 1.23 12 – 15 225 – 28145 (T3), Latency = 100ms 1.87 1.90 1.90 1.90 1.90 7 – 9 134 – 17445 (T3), Latency = 250ms 4.00 4.07 4.14 4.16 4.16 4 - 8 79 – 90 45 (T3), Latency = 500ms 7.50 7.50 7.70 7.90 7.90 2 – 4 35 - 4812 (8 T1s), Latency = 50ms 1.31 1.34 1.35 1.36 1.37 43 – 48 231 - 26012 (8 T1s), Latency = 100ms 2.03 2.03 2.04 2.07 2.08 30 – 32 156 - 18012 (8 T1s), Latency = 250ms 4.14 4.20 4.25 4.26 4.35 13 – 15 75 – 86 12 (8 T1s), Latency = 500ms 7.60 7.70 7.80 7.80 7.90 6 – 9 40 - 506 (Quad T1), Latency = 50ms 1.93 1.94 1.94 1.97 1.88 69 - 72 184 - 203
6 (Quad T1), Latency = 100ms 2.27 2.34 2.37 2.38 2.40 53 - 60 144 - 162
6 (Quad T1), Latency = 250ms 4.20 4.21 4.28 4.35 4.46 22 – 32 62 - 90
6 (Quad T1) Latency = 500ms 7.70 7.90 7.90 8.10 8.10 15 – 18 43 - 503 (Dual T1), Latency = 50ms 3.40 3.43 3.55 3.61 3.65 65 - 90 90 - 1243 (Dual T1), Latency = 100ms 3.57 3.59 3.68 3.69 3.72 64 – 85 88 - 1163 (Dual T1), Latency = 250ms 4.51 4.57 4.68 4.71 4.79 44 - 60 61 - 823 (Dual T1), Latency = 500ms 7.70 8.00 8.00 8.10 8.20 27 – 35 40 - 501.5 (T1), Latency = 50ms 6.40 7.20 7.40 7.50 7.50 85 - 95 62 - 661.5 (T1), Latency = 100ms 6.50 7.10 7.20 7.20 7.60 72 - 86 52 - 601.5 (T1), Latency = 250ms 7.00 7.10 7.20 7.30 7.40 75 – 84 52 - 601.5 (T1), Latency = 500ms 8.40 8.50 8.70 8.80 8.90 60 – 65 42 - 470.5 (512K), Latency = 50ms 18.20 18.90 20.40 20.40 22.00 80 – 98 19 - 240.5 (512K), Latency = 100ms 18.30 18.90 20.40 20.40 22.00 80 – 96 18 - 240.5 (512K), Latency = 250ms 18.50 18.80 19.60 20.80 21.10 78 - 90 21 - 240.5 (512K), Latency = 500ms 18.80 19.00 20.00 21.90 22.70 73 - 92 17 - 22
Page Load Time: Common User Operation
Wrap up… Key Considerations Reinforced.
Know your scenarios and how it will be usedIntranet publishing portalCollaborationBI Dashboards…
Know your networkBandwidthLatencyUtilization
Include tests and Surveys* from remote offices
Resources
www.microsoft.com/teched
Sessions On-Demand & Community Microsoft Certification & Training Resources
Resources for IT Professionals Resources for Developers
www.microsoft.com/learning
http://microsoft.com/technet http://microsoft.com/msdn
Learning
JUNE 7-10, 2010 | NEW ORLEANS, LA
Related Content
Breakout Sessions (session codes and titles)
Interactive Sessions (session codes and titles)
Hands-on Labs (session codes and titles)
Product Demo Stations (demo station title and location)
Complete an evaluation on CommNet and enter to win!
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to
be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.