Upload
thomas-vochten
View
464
Download
0
Tags:
Embed Size (px)
Citation preview
#comdaybe
Making Sense of SharePoint 2013
Thomas Vochten
About Me
Thomas Vochten
@thomasvochtenthomasvochten.comlinkedin.com/in/thomasvochten
SharePoint consultant. Platform architect. Speaker. Trainer. Accidental DBA.
SharePointSQL Server
Agenda
• SharePoint 2013 in perspective• 10 Essential things you need to
know• Towards a new reference
architecture
SharePoint 2013 in Perspective
Introduction
Architectural Changes
• No big leap from SharePoint 2010
• Service Application changes• New reference architecture
emerging• Motivation for most changes: The
Cloud
The Cloud…
The Cloud…
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
or BCS
Typical Use Case: Hybrid Search
Graphic © Microsoft
New Service Applications
• Machine Translation• Work Management• App Management
System Requirements
SharePoint
CPU 64 bit, 4 coreRAM 12 GBDisk 80 GB
SQL Server
CPU 64 bit, 4 coreRAM 8 GBDisk 80 GB
* Minimal requirements
Software Requirements
SharePoint
• Windows Server 2012
• Windows Server 2008 R2 with SP1
SQL Server
• SQL Server 2012• SQL Server 2008
R2 with SP1
Client Software Requirements
Graphic © 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 functionalities are
huge• Numerous functional
improvements
Logical Architecture
Graphic © Microsoft
Crawling
• Does not do indexing anymore• Only delivers content for further
processing• Continuous Crawl
Graphic © Microsoft
Content Processing
• Document parsing• Property parsing• Links & URL parsing• Linguistics
Graphic © Microsoft
Analytics Processing
• Replaces Web Analytics from 2010
• User interaction analysis
Indexing
• Index Partitions• Replicas
Graphic © Microsoft
Query Processing
• Receives and handles queries
Graphic © Microsoft
Search Processes
• hostcontroller.exe• noderunner.exe• mssearch.exe
Graphic © Microsoft
demoA quick look
Search Administration
Distributed Cache
What are we trying to solve?
• Asynchronous is king• A lot of interactivity• Sticky sessions were a pain• Minimizing database calls
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
Managing the Cache
PowerShell, what else
• Stop/Start• Change Memory allocation
demoManaging the cache
Distributed Cache
Shredded Storage
What are we trying to solve?
• Reducing IO operations• Reducing storage capacity• Better performance
Shredded Storage
• Evolution of the Cobalt protocol in 2010
• SharePoint feature, not SQL feature
• Files are shredded into different blobs
• Only changed blobs are written back to the database
Nice to know
• Cannot be turned off• Files are not shredded after
upgrade, only on first change• Shredded storage also works
with RBS
demoHow it looks inside SQL Server
Shredded Storage
Office Web Apps
What are we trying to solve?
Graphic © Microsoft
Office Web Apps
Graphic © Microsoft
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
demoWhat it looks like & how to connect to SharePoint
Office Web Apps
Workflow Engine
What are we trying to solve?
• 2010 Workflows ran in-process with your content
• Limited scalability options
Workflow Engine
• Workflow as a service• Workflow Manager & Service Bus• Can run independently from
SharePoint• Designed with the cloud in mind• Separate databases
Request Management
What are we trying to solve?
• Very limited control over web requests coming into SharePoint
• Load balancing as only option• Throttling capabilities in 2010
rather limited
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 other requests• Routing according to request types• Isolate requests to a specific server …
Request Mgmt Flow
Graphic © Spencer Harbar
Apps Model
What are we trying to solve?
How to develop for SharePoint 2013
• Farm solutions• Sandboxed solutions• Apps
Lists & libraries are also Apps now
---------------------- deprecated
Apps to the rescue
Freedom to use any technology you like
Graphic © Microsoft
Hosting Apps
Graphic © Microsoft
SharePoint Hosted Apps
• Still a valid option• Supporting service applications:
Apps Mgmt ServiceSubscription Mgmt Service
• Requires specific infrastructure
Infrastructure for SharePoint Hosted Apps
• Separate Web Application• Separate DNS domain & wildcard A
record due to URL structure
• SSL is mandatory in production• Apps Management Service configuration
Graphic © Microsoft
Managing Apps
• Deployed from corporate catalog or SharePoint store
• Manage permission and licenses specifically
• Simple install and upgrade process
demoSharePoint (Hosted) Apps
Upgrade
What are we trying to solve?
• Problems during upgrade process• Downtime during upgrade• Little freedom to keep user
interface untouched• Few options for site owners to
prepare for upgrade
Upgrade to SharePoint 2013
v2v 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 Event Notifications System• Logging Changes• Site Collection Upgrade Throttling• Federated Services Compatibility
Cross Versions
Authentication
User Authentication
• Claims is the default• Classic is deprecated, only via
PowerShell• FedAuth cookie now stored in
cache
Server Authentication
OAuth
• Approve an app to act on your behalf
• Does not share usernames or passwords
• Provides app access to SharePoint data
The Way ForwardTowards a new reference architecture
Emerging Practices
• Consolidation of resources
less web applicationsless application pools
• Host named site collections
Q&A
Thank you!
@thomasvochten#comdaybe