A review of the new features in SharePoint 2013. For more information: www.adventos.com Twitter: @AdventosSolves -- https://twitter.com/adventossolves Facebook: @AdventosLLC -- https://www.facebook.com/AdventosLlc

1. SharePoint 2013: What’s New

2. Overview of High-Level Changes

3. New Service Applications
• Translation Service
– Cloud-based
– Translates sites and their content
– Can be pre-translated or translated by users
• PowerPoint Automation Service
– Similar to Word Automation Service
– Converts PowerPoint to newer Office documents, web pages, or
PDFs
• App Management Service
– Manages applications, permissions, and licensing
– Can install from SharePoint Marketplace or Internal App
Directory

4. Add App

5. New Services
• Work Management Service
– Connects servers across the organization
– Action-based event aggregation
– Exchange Server, Lync Server, Project
Server, and SharePoint Server
– e.g. Enter tasks from mobile phone into
Exchange and tasks display in My Tasks in
SharePoint

6. My Tasks

7. Improved Service Apps
• Office Web Apps
– Separate server product
– Can serve multiple farms for viewing and
editing
– Can view files stored across data stores
• Exchange, Lync, SharePoint
• File servers
– Can integrate with third-party stores
• EMC Documentum, IBM FileNet, OpenText, Oracle
– Managed independently of SharePoint

8. Improved Services
• User Profile Service
– Simplifies access to user properties
– New profile import options
• Forefront Identity Manager-based import
• Direct AD Domain Services synchronization
• External identity manager
– Significant performance improvements

9. Improved Scalability
• Scalable architecture
– Easier to deploy a single, valuable project and
then easily scale vertically and horizontally
• Distributed cache
– Faster response time
• Disk I/O
– Can be deployed to a variety of storage
architectures
– Better performance in disk I/O and
contentions

10. Improved Scalability
• Shredded storage
– Enables storage of incremental updates
– Write costs for file update based on changes to
file rather than the size of entire file
– Stores file in pieces in SQL Server
• Minimal download
– Entire page is not rendered—user receives only
updates to the page
– Developers can also write more efficient solutions
since they have access to the same framework

11. Improved Scalability
• Data Platform – better performance
– Removes redundant and unused tables and
indices
– Reduced I/O for browsing libraries
– Simplifies database schemas and access
– Improves large list dependencies
• Social Computing
– Data stored in content database with personal
sites

12. Risk Management - Security
• Information Management
– Corporate-wide policies can be applied to site
collections
• Electronic Discovery
– Integrated information archiving, retention,
and discovery capabilities
• Rights Management
– Controls who read or copies information, no
matter where it is stored

13. Security
• Secure Delegation
– Delegate permissions either server-to-server
or application level
– Supports OAuth 2.0 support (―act on behalf
of‖ permission)
• Site Closure and Deletion
– IT can create policies for archiving
• iFrame Security
– Admins can set rights for iFrame usage

14. Reliability
• Request Management
– IT can use rules to prioritize and route
requests
– Can route request to best server for response
– Can block known bad requests
– Route specific requests to other servers—
even outside the farm
– Throttle lower-priority requests to preserve
resources for higher-priority requests

15. Reliability
• System Status Notifications
– Information to users about deployment,
upgrades, maintenance, or conversions

16. Reliability
• Developer Dashboard
– Information about performance and reliability

17. Cost Effective – Reduce IT Costs
• Deferred Upgrade
– Upgrade server but allow site collection
administrators to choose when they want to
upgrade
• Site Collection Health Checks
– Users can run to detect issues and get
resolutions prior to upgrading
• Selective Provisioning
– Can deploy 2013 to either 2010 or 2013
mode

18. Cost Effective
• Windows PowerShell
– SharePoint includes native support
• Central Administration
– Role-based model to distribute responsibilities
• E.g. Help Desk staff

19. Efficiency
• Multiple Devices
– Consistent experience across screens
• Open Data Protocol
– Supports Open Data Protocol (OData)
• Allows users to take information outside of
application boundaries
• Integration and interoperability across clients,
servers, and services

20. Efficiency - BCS
• Pull Model (custom code event receivers)
– Can develop BDC model that subscribes to
published events from external system
– Users can receive alerts from external
systems
• External lists can be exported to Excel
– Exports the view (filtering and sorting)
– One way link
– Offloads retrieval, paging, sorting and filtering
onto the external system

21. Efficiency - Search
• New search engine
– Includes scale and extensibility of FAST
Search

22. Efficiency – Business Intelligence
• Visualizations through Power View
Reports
• Easier to explore data through Excel
Services
• Tighter security
• Supports multiple devices
• Supports multiple platforms
– On-premise and cloud

23. Dashboard

24. Overview of
Developer Changes

25. Solution Types
• Many changes for developers
• Sandboxed solutions are deprecated
– Replaced with apps
– Apps removed restrictions that existed with
sandboxed solutions
• Apps are displayed in Site Contents with other
SharePoint artifacts (e.g. document library)
• Site Owner can ―Add an App‖ to their Site
Contents
• Apps can run both in the cloud and on premise
(they are not full-trust)

26. Site Contents

27. Full Page App
Link back

28. App Hosting Options
• Apps can run separately from SharePoint
environment
• You just have to provide the resources (e.g. web
hosting, processing power and if needed, data
storage)
• ―External engine‖ can talk to SharePoint
– Use client APIs – CSOM and REST
– Use OAuth for authentication (token-based)
– Can read and/or modify SharePoint data
– Code-intensive application does not affect the
performance of SharePoint

29. App Hosting Options
• Remote – Azure
– Integrated into app deployment process
– Infrastructure is created to Azure and deployed in
SharePoint
– Can include SQL Azure to store data
• Remote – Developer hosted
– Whoever builds the app provides the hosting and
infrastructure
– Could be another SharePoint farm, another
server running IIS, Amazon Web Services, etc.
– Access SharePoint through CSOM or REST

30. App Hosting Options
• On Premise SharePoint Hosted
– Server-side code is NOT permitted
• CSOM or REST, HTML, CSS, or JavaScript
– SharePoint artifacts used by app do not exist in
site collection where app is installed
• They are created in a separate web app which is
isolated from the site collection (Visual Studio
understands architecture)
• Can still create standard SharePoint solutions if
client APIs cannot do what you need
– Farm
– Sandbox

31. Workflows
• Workflows no longer run in the SharePoint
process
• Run by Workflow Manager (Windows
Azure Workflow)
– Makes HTTP REST requests to SharePoint
• Workflow Manager can be installed on a
separate server
• Workflows can be scaled independently of
SharePoint

32. Access Applications
• Developer tool for power user
• Web front end
• SQL Server back end
• Access Services in the middle
• Metro style UI

33. CSOM
• Can access many New APIs with SharePoint Server
functionality – They are all available in
services in addition to Sever Side .NET CSOM and REST
SharePoint sites based APIs:
– e.g. Search, Metadata,
User Profiles (no need to use User
Translation, User Profiles ASMX for remote calls)
Profiles Search (no need to use
– Works with .NET, Search.ASMX for remote calls)
Taxonomy
Silverlight, and Feeds
ECMAScript Publishing
Sharing
Workflow
E-Discovery
IRM
Analytics
BCS

34. CSOM Model

35. REST API
• REST endpoints correspond to APIs in CSOM
• Can interact with SharePoint by any technology
that supports REST
• Use RESTful HTTP requests using Open Data
Protocol (OData) standard
– Reads are an HTTP GET
– Writes are either an HTTP PUT or HTTP POST
– Deletes are HTTP DELETE
• Responses are in either Atom or JSON
– Client app must parse the response

36. REST Service Access Points
Area Access Point
Site http://server/site/_api/site
Web http://server/site/_api/web
http://
User Profile
server/site/_api/SP.UserProfiles.PeopleManager
Search http:// server/site/_api/search
Publishing http:// server/site/_api/publishing

37. CSOM & REST Equivalents
Client Object Model REST Equivalent
ClientContext.Web.Lists http://server/site/_api/web/lists
ClientContext.Web.Lists[guid] http://server/site/_api/web/lists(‗guid‘)
http://server/site/_api/web/lists/getby
ClientContext.Web.Lists.GetByTitle("Title")
title(‗Title‘)

38. OData Query Operators
Supported Not Supported
Numeric Comparisons
•Lt
•Le •Arithmetic operators
•Gt (Add, Sub, Mul, Div, Mod)
•Ge •Basic math functions
•Eq (round, floor, ceiling)
•Ne
•endsWith
String Comparisons
•replace
•startsWith
•substring
•substringof
•tolower
•Eq
•toupper
•Ne
•trim
•concat
Date & Time Functions
•day()
•month()
•DateTimeRangesOverlap operator
•year()
•Querying as to whether a date time
•hour()
falls inside a recurrent date time
•minute()
•second()