• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
20130427 - Turbocharge SharePoint 2010 with SharePoint 2013 Search
 

20130427 - Turbocharge SharePoint 2010 with SharePoint 2013 Search

on

  • 2,645 views

Presented at SharePoint Saturday Boston

Presented at SharePoint Saturday Boston

Statistics

Views

Total Views
2,645
Views on SlideShare
2,638
Embed Views
7

Actions

Likes
2
Downloads
0
Comments
0

1 Embed 7

https://twitter.com 7

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Timings0:00 – 0:05 – Introduction to Compare (Both)0:05 – 0:20 – FAST Good, Bad, and Ugly and Architecture (Neal)0:20 – 0:25 – Three Approaches (Bob)0:25 – 0:35 – Approach #1 (Bob)0:35 – 0:45 – Approach #2 (Neal)0:45 – 0:55 – Approach #3 (Bob)0:55 – 1:00 – Wrap-up (Both)
  • Show:SP2013 Central Admin – Search ServiceSP2013 Central Admin – Permissions on Search ServiceSP2010 Central Admin – Consuming Search ServiceSp2010 Search Center – Demonstrate results
  • Show:SP2010 Site – Configure results pageDo a search – go to SP2013 Search Center – Demonstrate results
  • Show:SP2013 Search Service – Show file share crawl, file countsSP2010 Central Admin – Search Service, federated locationSP2010 Search Center – Demonstrate results

20130427 - Turbocharge SharePoint 2010 with SharePoint 2013 Search 20130427 - Turbocharge SharePoint 2010 with SharePoint 2013 Search Presentation Transcript

  • Turbocharge SharePoint 2010with SharePoint 2013 SearchBob German – SharePoint Practice Director, BlueMetal ArchitectsNeal McFee – Technical Advisor, Harvard Business School@SPSBoston - @Bob1German - @sharepointmcts
  • SharePoint PracticeDirector@Bob1Germanhttp://blogs.msdn.com/BobGerman/Meet Neal and BobTechnical Advi@sharepointmctshttp://www.sharepointfeed.com@SPSBoston - @Bob1German - @sharepointmcts
  • A Tale of Two Search EnginesESP for SharePoint• Licensing deal for FAST andSharePoint 2007• Used FAST’s originalSharePoint integrationFAST Search for SharePoint• Common crawl and querycomponents• FAST and SharePoint farmstightly integratedSharePoint 2013 Search• One search engine• One farm• Simple, easy, powerful@SPSBoston - @Bob1German - @sharepointmctsB
  • SharePoint 2010Enterprise Search vs.FAST Search for SharePoint@SPSBoston - @Bob1German - @sharepointmctsB
  • Comparing the Search Engines2010 Enterprise Search 2010 FAST Search 2013 SearchRefiners X X XDeep Refiners X XHigh degree ofrelevancyX XMultitenant X XRANK / XRANK * X * xrank onlySoundex People Search X XBest Bets (good) XVisual Best Bets (better) XPromoted Results (best) XEntity Extraction X X@SPSBoston - @Bob1German - @sharepointmcts
  • FAST – The Good, The Bad, and The Ugly “Deep” Refiners (refiners takewhole result set into account) Entity Extraction Exact hit counts Content previews (with OfficeWeb Applications) Visual Best Bets Complex configuration Single purpose – no multi-tenancy Difficult to manage Can’t be managed by sitecollection administrator Additional hardwareinvestmentThe Good The Bad and The Ugly@SPSBoston - @Bob1German - @sharepointmctsN
  • FAST for SharePoint 2010 Architecture@SPSBoston - @Bob1German - @sharepointmctsFAST Query SSAQuery ProcessingFAST Content SSASharePoint SitesWeb SitesFile SharesDatabasesBusiness AppsQuery MatchingFAST Search AuthorizationSearch IndexItem ProcessingIndexingFAST Specific ConnectorsWeb AnalyzerAdministrationLogical ArchitecturePhysical ArchitectureSharePoint Server 2010(Medium Farm)FAST Search for SharePointFAST Search for SharePoint(Small Deployment)SharePoint Server 2010 Search RequestWFE WFEAPPSQLAdministrationDocument ProcessingSQLSearch Administration DatabaseCrawl DatabaseBackup IndexerContent DistributorIndexing DispatcherDocument ProcessingWeb AnalyzerQuery ServerSQLSQLPrimary IndexerContent DistributorIndexing DispatcherDocument ProcessingWeb AnalyzerQuery ServerN
  • SharePoint 2013 Search ArchitectureContent UXAPIContentEnrichmentWeb ServicePublic APIUnit of scale/role boundaryExtensibility Points• HTTP• File shares• SharePoint• User profiles• Lotus Notes• Documentum• Exchange folders• Custom - BCS• SharePoint• SP Apps• Devices• Non-SP UX@SPSBoston - @Bob1German - @sharepointmctsB
  • Search First Migration1. Set up SharePoint 2013 Farm2. Set up (or migrate) SharedService In this case, we’ll crawl the SP2010 farm froma new SP2013 SSA3. Consume the SP2013 servicefrom SharePoint 2010Notes: Works because Service Applicationarchitecture is the same for 2010 and 2013 Users and content stay in SharePoint 2010 –no user impact Business Data Connectivity Managed Metadata PerformancePoint Services Search Secure Store User Profile Search Upgrade Options:1. Manually re-create2. DB Attach (Admin DB only)3. Migration scripts (from FAST 2010 only – seehttp://bit.ly/Search1ScriptsMigrating Shared Services Services that Support UpgradeB
  • Three ApproachesBContent Search Engine Search CenterApproach 1 SharePoint2010SharePoint2013SharePoint2010Approach 2 SharePoint2010SharePoint2013SharePoint2013Approach 3 Anything SharePoint2013SharePoint2010Federation
  • Approach 1: 2010 Search Center consumes 2013 Recommended byMicrosoft as part of“Search First” migration Enable FAST features withminimal disruptionDeep RefinersPreviews work out of the box 2013 farm hardwarerequirements similar toFAST farmInvest in hardware once No way to take advantageof new SharePoint 2013Search UI featuresResult TypesDisplay TemplatesPro ConB
  • Approach 1:SharePoint 2010 Search CenterConsumes 2013 SSAdemoB
  • Approach 1: 2010 Search Center consumes 2013@SPSBoston - @Bob1German - @sharepointmctsQuery processingAnalyticsProcessingContent processingSearch AdminIndexCrawlContent Sourceshttp://sp2010.contoso.comsps3://sp2010.contoso.comSP2013 Search Service ApplicationSharePoint 2010 Web ApplicationCrawl ContentAssociate the Connected SP2013Search Service Application Proxyto the SharePoint 2010 WebApplicationSharePoint 2010 Farm SharePoint 2013 Farmsps3://sp2010.contoso.comSharePoint 2010 User Profile SAhttp://sp2010.contoso.comThe SharePoint 2010 SearchCenter displays results from theconnected SP2013 Search ServiceApplicationB
  • Approach 1: 2010 Search Center consumes 2013 SharePoint 2010 Server EnterpriseEdition (for FAST Search Center) SharePoint 2013Standard works fineEnterprise adds:Custom Entity ExtractionExtensible Content Processing(other features which aren’t visiblefrom SP2010)1. Set up Search SA on SharePoint20132. Crawl the 2010 farm from the newSSA Configure managed properties and othersettings3. Exchange trust certificates betweenfarms4. Publish the SharePoint 2013 SSA5. Grant the SP2010 farm access to thefollowing SP2013 SA’s: Application Discovery and Load Balancing Search6. Connect the SP2010 to the 2013SSA7. Associate the 2013 SSA proxy withthe 2010 Web ApplicationProducts Shown Setup StepsB
  • Approach 2: Redirect to 2013 Search Center Enjoy full SP2013 searchexperienceDeep RefinersResult TypesDisplay TemplatesQuery Rules 2013 farm hardwarerequirements similar toFAST farmInvest in hardware once Extra work required to getOffice previews to work Users may find transition tothe SP2013 UI to be jarringPro ConN
  • Approach 2:Redirect to SP2013 Search CenterdemoN
  • Approach 2: Redirect to 2013 Search Center@SPSBoston - @Bob1German - @sharepointmctsSharePoint 2010 Web ApplicationCrawl ContentSharePoint 2010 Farm SharePoint 2013 FarmQuery processingAnalyticsProcessingContent processingSearch AdminIndexCrawlContent Sourceshttp://sp2010.contoso.comsps3://sp2010.contoso.comSP2013 Search Service Applicationhttp://sp2010.contoso.comSharePoint 2013 Search CenterCustom Search Scope redirect to SharePoint 2013 Search CenterThe SharePoint 2013 Search Centerdisplays results from crawledSharePoint 2010 contentsps3://sp2010.contoso.comSharePoint 2010 User Profile SSAN
  • Approach 2: Redirect to 2013 Search Center SharePoint 2010 Server (Standardor Enterprise) SharePoint 2013Standard works fineEnterprise adds:Custom Entity ExtractionExtensible Content ProcessingAdvanced actions on Query RulesVideo Search1. Set up Search SA on SharePoint20132. Crawl the 2010 farm from the newSSA Configure managed properties and othersettings3. Set up a search center onSP20134. (optional) For Office previews: Set up an OWA 2013 server Modify SP2013 display templates asexplained here: http://bit.ly/Search1Previews/5. On SP2010, set results page topoint to SP2013 search centerProducts Shown Setup StepsN
  • Approach 3: Federate with 2013 Search Most useful with externalcontent Not disruptive – users seefamiliar SP2010 UI 2013 farm hardwarerequirements similar toFAST farm Federation works well overslow WAN connections Results appear side byside, not reflected inrefiners, no previews No distinct advantage overApproach 1 for SharePointcontentPro ConB
  • Approach 3:Federate with SP2013 SearchCenterdemoB
  • Approach 3: Federate with 2013 Search@SPSBoston - @Bob1German - @sharepointmctsSharePoint 2010 Web ApplicationSharePoint 2010 Farm SharePoint 2013 FarmExternal ContentQuery processingAnalyticsProcessingContent processingSearch AdminIndexCrawlContent Sourcesfile://server/folderSP2013 Search Service ApplicationContentCrawlCrawlAdminhttp://sp2010.contoso.comsps3://sp2010.contoso.comContent SourcesIndexSP2010 Search Service ApplicationFederated Location QueryReturnContentsps3://sp2010.contoso.comSharePoint 2010 User Profile SSAhttp://sp2010.contoso.comCrawlB
  • Approach 3: Federate with 2013 Search SharePoint 2010 Server (Standardor Enterprise) SharePoint 2013Standard works fineEnterprise adds:Custom Entity ExtractionExtensible Content Processing(other features which aren’t visiblefrom SP2010)1. Set up Search SA on SharePoint20132. Crawl the external content fromthe new SSA Configure managed properties and othersettings3. Set up a search center in SP20134. Ensure Kerberos is in place if youwant security trimming5. On SP2010, add a federatedlocation for the SP2013 searchcenter6. Configure the Federated Resultsweb part on SP2010Products Shown Setup StepsB
  • Choosing an ApproachApproach 1:2010 Search CenterConsume 2013 ServiceApproach 2:2013 Search CenterNative 2013 ServiceApproach 3:2010 Search CenterFederate to 2013Key Scenario FAST Capabilities withminimal disruptionFull 2013 UserExperienceSpecialized contentsourcesGlobal Deployment Low latency between2010 and 2013 farmsMedium latencybetween 2010 and 2013farmsHigh latency / lowbandwidth OK between2010 and 2013 farmsBranding Preserve current lookand feelJump into SP2013 lookand feelPreserve current lookand feelSecurity Read access to allcontentRead access to allcontentProvide secured searchservice without accessto all content@SPSBoston - @Bob1German - @sharepointmcts
  • Summary If you haven’t moved to FAST, there areseveral good reasons to move directlyto SP2013 Search: Easier to set up and maintain First step in migrating to SP2013 Able to phase in new SP2013 user experience Better documentation Brighter future Similar hardware footprint and cost (softwarelicenses will vary depending on your agreementwith Microsoft) Choose an approach that bestmeets your needshttp://bit.ly/Search1Newhttp://bit.ly/Search1PromotedResultshttp://bit.ly/Search1Editionshttp://bit.ly/Search1Farmshttp://bit.ly/Search1CrossFarmhttp://bit.ly/Search1Previewshttp://bit.ly/Search1Scripts@SPSBoston - @Bob1German - @sharepointmcts
  • Thank you!@SPSBoston - @Bob1German - @sharepointmcts