#comdaybeMaking Sense of SharePoint 2013Thomas Vochten
About MeSharePointconsultant. Platformarchitect. Speaker.Trainer. AccidentalDBA.
Agenda• SharePoint 2013 in perspective• 10 Essential things you need to know• Towards a new reference architecture
SharePoint 2013 inPerspectiveIntroduction
Architectural Changes• No big leap from SharePoint 2010• Service Application changes• New reference architecture emerging•...
The Cloud…
The Cloud…
Living in a hybrid world• Cloud for collaboration• On-Premises for special needs• Single Sign On• Server-to-Server trust w...
Typical Use Case: Hybrid SearchGraphic © Microsoft
New Service Applications• Machine Translation• Work Management• App Management
System RequirementsSharePointCPU 64 bit, 4 coreRAM 12 GBDisk 80 GBSQL ServerCPU 64 bit, 4 coreRAM 8 GBDisk 80 GB* Minimal ...
Software RequirementsSharePoint• Windows Server 2012• Windows Server 2008R2 with SP1SQL Server• SQL Server 2012• SQL Serve...
Client Software RequirementsGraphic © Microsoft
Client Software Requirements• Office 2013• SharePoint Designer 2013• SkyDrive Pro* Most Office 2010 equivalents will do
Search
Search in 2013• Complete overhaul• Based upon 2010 & FAST technology• Only one search product left!• Search-driven functio...
Logical ArchitectureGraphic © Microsoft
Crawling• Does not do indexing anymore• Only delivers content for furtherprocessing• Continuous CrawlGraphic © Microsoft
Content Processing• Document parsing• Property parsing• Links & URL parsing• LinguisticsGraphic © Microsoft
Analytics Processing• Replaces Web Analytics from 2010• User interaction analysis
Indexing• Index Partitions• ReplicasGraphic © Microsoft
Query Processing• Receives and handles queriesGraphic © Microsoft
Search Processes• hostcontroller.exe• noderunner.exe• mssearch.exeGraphic © Microsoft
demoA quick lookSearch Administration
Distributed Cache
What are we trying to solve?• Asynchronous is king• A lot of interactivity• Sticky sessions were a pain• Minimizing databa...
What is it?• Based on Appfabric• On by default on all servers• Contributes to the larger footprint• Powered by a Windows s...
Managing the CachePowerShell, what else • Stop/Start• Change Memory allocation
demoManaging the cacheDistributed Cache
Shredded Storage
What are we trying to solve?• Reducing IO operations• Reducing storage capacity• Better performance
Shredded Storage• Evolution of the Cobalt protocol in2010• SharePoint feature, not SQL feature• Files are shredded into di...
Nice to know• Cannot be turned off• Files are not shredded after upgrade,only on first change• Shredded storage also works...
demoHow it looks inside SQL ServerShredded Storage
Office Web Apps
What are we trying to solve?Graphic © Microsoft
Office Web AppsGraphic © Microsoft
Office Web Apps 2013• Separate product, unified platform• Separate server farm• More operational choices & freedom• Word, ...
demoWhat it looks like & how to connect toSharePointOffice Web Apps
Workflow Engine
What are we trying to solve?• 2010 Workflows ran in-process withyour content• Limited scalability options
Workflow Engine• Workflow as a service• Workflow Manager & Service Bus• Can run independently fromSharePoint• Designed wit...
Request Management
What are we trying to solve?• Very limited control over webrequests coming into SharePoint• Load balancing as only option•...
Request Management• Powerful routing & throttling rules• Customized responses• Per web application• Not activated by default
Scenario’s• Routing according to server health• Identification of dangerous requests• Prioritize requests over otherreques...
Request Mgmt FlowGraphic © Spencer Harbar
Apps Model
What are we trying to solve?How to develop for SharePoint 2013• Farm solutions• Sandboxed solutions• AppsLists & libraries...
Apps to the rescueFreedom to use any technology youlikeGraphic © Microsoft
Hosting AppsGraphic © Microsoft
SharePoint Hosted Apps• Still a valid option• Supporting service applications:Apps Mgmt ServiceSubscription Mgmt Service• ...
Infrastructure for SharePointHosted Apps• Separate Web Application• Separate DNS domain & wildcard Arecord due to URL stru...
Managing Apps• Deployed from corporate catalog orSharePoint store• Manage permission and licensesspecifically• Simple inst...
demoSharePoint (Hosted) Apps
Upgrade
What are we trying to solve?• Problems during upgrade process• Downtime during upgrade• Little freedom to keep user interf...
Upgrade to SharePoint 2013v2v Upgrade methods:• Gradual Upgrade• In-Place Upgrade• Database Attach Upgrade----------------...
Prepare for Upgrade• Test-SPContentDatabase• Migrate to claims before upgrade
Improvements• Deferred Site Collection Upgrade• Site Collection Health Checks• Upgrade Evaluation Site Collections• System...
Authentication
User Authentication• Claims is the default• Classic is deprecated, only viaPowerShell• FedAuth cookie now stored in cache
Server AuthenticationOAuth• Approve an app to act on your behalf• Does not share usernames orpasswords• Provides app acces...
The Way ForwardTowards a new reference architecture
Emerging Practices• Consolidation of resourcesless web applicationsless application pools• Host named site collections
Q&A
Thank you!@thomasvochten#comdaybe
Upcoming SlideShare
Loading in...5
×

Making sense of SharePoint 2013

484

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
484
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • How it looksHow to connectEven PDF’s can be opened! Preview is also possible with some work
  • WF improvements: stages, loops, call webservices
  • SharePoint throttling leaves it up to the client to act upon a health score.
  • Regular expression can filter on all HTTP header values like CustomHeaderHost HttpMethodIP SoapActionUrlUrlReferrerUserAgent
  • Throttle heavy Excel or OneNote requests in favor of normal web requests
  • Apps are rendered in SharePoint in html or inside an iFrameApps can be made to look just like SharePoint
  • No custom code on SharePoint server anymore but still allowing maximum flexibility.
  • V2V: only database attachB2B: in place still possibleAlmost all service app databases support database attach
  • Think Office365 for all these improvements!Deferred: keep the 2010 UI / 2013 has full 2010 engine aboard (replaces visual upgrade) / the default when upgrading!Health Checks: see if your sitecollection has problems, common known issuesEval: try out a copy of your site
  • Making sense of SharePoint 2013

    1. 1. #comdaybeMaking Sense of SharePoint 2013Thomas Vochten
    2. 2. About MeSharePointconsultant. Platformarchitect. Speaker.Trainer. AccidentalDBA.
    3. 3. Agenda• SharePoint 2013 in perspective• 10 Essential things you need to know• Towards a new reference architecture
    4. 4. SharePoint 2013 inPerspectiveIntroduction
    5. 5. Architectural Changes• No big leap from SharePoint 2010• Service Application changes• New reference architecture emerging• Motivation for most changes: TheCloud
    6. 6. The Cloud…
    7. 7. The Cloud…
    8. 8. Living in a hybrid world• Cloud for collaboration• On-Premises for special needs• Single Sign On• Server-to-Server trust with OAuth• Typical use cases: hybrid search orBCS
    9. 9. Typical Use Case: Hybrid SearchGraphic © Microsoft
    10. 10. New Service Applications• Machine Translation• Work Management• App Management
    11. 11. System RequirementsSharePointCPU 64 bit, 4 coreRAM 12 GBDisk 80 GBSQL ServerCPU 64 bit, 4 coreRAM 8 GBDisk 80 GB* Minimal requirements
    12. 12. Software RequirementsSharePoint• Windows Server 2012• Windows Server 2008R2 with SP1SQL Server• SQL Server 2012• SQL Server 2008 R2with SP1
    13. 13. Client Software RequirementsGraphic © Microsoft
    14. 14. Client Software Requirements• Office 2013• SharePoint Designer 2013• SkyDrive Pro* Most Office 2010 equivalents will do
    15. 15. Search
    16. 16. Search in 2013• Complete overhaul• Based upon 2010 & FAST technology• Only one search product left!• Search-driven functionalities are huge• Numerous functional improvements
    17. 17. Logical ArchitectureGraphic © Microsoft
    18. 18. Crawling• Does not do indexing anymore• Only delivers content for furtherprocessing• Continuous CrawlGraphic © Microsoft
    19. 19. Content Processing• Document parsing• Property parsing• Links & URL parsing• LinguisticsGraphic © Microsoft
    20. 20. Analytics Processing• Replaces Web Analytics from 2010• User interaction analysis
    21. 21. Indexing• Index Partitions• ReplicasGraphic © Microsoft
    22. 22. Query Processing• Receives and handles queriesGraphic © Microsoft
    23. 23. Search Processes• hostcontroller.exe• noderunner.exe• mssearch.exeGraphic © Microsoft
    24. 24. demoA quick lookSearch Administration
    25. 25. Distributed Cache
    26. 26. What are we trying to solve?• Asynchronous is king• A lot of interactivity• Sticky sessions were a pain• Minimizing database calls
    27. 27. What is it?• Based on Appfabric• On by default on all servers• Contributes to the larger footprint• Powered by a Windows service• 10% of server memory by default• Scalable
    28. 28. Managing the CachePowerShell, what else • Stop/Start• Change Memory allocation
    29. 29. demoManaging the cacheDistributed Cache
    30. 30. Shredded Storage
    31. 31. What are we trying to solve?• Reducing IO operations• Reducing storage capacity• Better performance
    32. 32. Shredded Storage• Evolution of the Cobalt protocol in2010• SharePoint feature, not SQL feature• Files are shredded into different blobs• Only changed blobs are written backto the database
    33. 33. Nice to know• Cannot be turned off• Files are not shredded after upgrade,only on first change• Shredded storage also works withRBS
    34. 34. demoHow it looks inside SQL ServerShredded Storage
    35. 35. Office Web Apps
    36. 36. What are we trying to solve?Graphic © Microsoft
    37. 37. Office Web AppsGraphic © Microsoft
    38. 38. Office Web Apps 2013• Separate product, unified platform• Separate server farm• More operational choices & freedom• Word, Excel, PowerPoint, OneNote• Claims mode only• Clean URLs• Licensing options
    39. 39. demoWhat it looks like & how to connect toSharePointOffice Web Apps
    40. 40. Workflow Engine
    41. 41. What are we trying to solve?• 2010 Workflows ran in-process withyour content• Limited scalability options
    42. 42. Workflow Engine• Workflow as a service• Workflow Manager & Service Bus• Can run independently fromSharePoint• Designed with the cloud in mind• Separate databases
    43. 43. Request Management
    44. 44. What are we trying to solve?• Very limited control over webrequests coming into SharePoint• Load balancing as only option• Throttling capabilities in 2010 ratherlimited
    45. 45. Request Management• Powerful routing & throttling rules• Customized responses• Per web application• Not activated by default
    46. 46. Scenario’s• Routing according to server health• Identification of dangerous requests• Prioritize requests over otherrequests• Routing according to request types• Isolate requests to a specific server…
    47. 47. Request Mgmt FlowGraphic © Spencer Harbar
    48. 48. Apps Model
    49. 49. What are we trying to solve?How to develop for SharePoint 2013• Farm solutions• Sandboxed solutions• AppsLists & libraries are also Apps now ---------------------- deprecated
    50. 50. Apps to the rescueFreedom to use any technology youlikeGraphic © Microsoft
    51. 51. Hosting AppsGraphic © Microsoft
    52. 52. SharePoint Hosted Apps• Still a valid option• Supporting service applications:Apps Mgmt ServiceSubscription Mgmt Service• Requires specific infrastructure
    53. 53. Infrastructure for SharePointHosted Apps• Separate Web Application• Separate DNS domain & wildcard Arecord due to URL structure• SSL is mandatory in production• Apps Management Service configurationGraphic © Microsoft
    54. 54. Managing Apps• Deployed from corporate catalog orSharePoint store• Manage permission and licensesspecifically• Simple install and upgrade process
    55. 55. demoSharePoint (Hosted) Apps
    56. 56. Upgrade
    57. 57. What are we trying to solve?• Problems during upgrade process• Downtime during upgrade• Little freedom to keep user interfaceuntouched• Few options for site owners toprepare for upgrade
    58. 58. Upgrade to SharePoint 2013v2v Upgrade methods:• Gradual Upgrade• In-Place Upgrade• Database Attach Upgrade--------------------------------------------
    59. 59. Prepare for Upgrade• Test-SPContentDatabase• Migrate to claims before upgrade
    60. 60. Improvements• Deferred Site Collection Upgrade• Site Collection Health Checks• Upgrade Evaluation Site Collections• System Event Notifications System• Logging Changes• Site Collection Upgrade Throttling• Federated Services Compatibility CrossVersions
    61. 61. Authentication
    62. 62. User Authentication• Claims is the default• Classic is deprecated, only viaPowerShell• FedAuth cookie now stored in cache
    63. 63. Server AuthenticationOAuth• Approve an app to act on your behalf• Does not share usernames orpasswords• Provides app access to SharePointdata
    64. 64. The Way ForwardTowards a new reference architecture
    65. 65. Emerging Practices• Consolidation of resourcesless web applicationsless application pools• Host named site collections
    66. 66. Q&A
    67. 67. Thank you!@thomasvochten#comdaybe
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×