1. Microsoft SharePoint 2013 SharePoint 2013 Solution Highlights
SharePoint Practice

2. What is SharePoint?
“SharePoint is an extensible and scalable web-based platform consisting of tools and technologies that support the collaboration and sharing of information within teams, throughout the enterprise, and on the web.”
“SharePoint improves end user productivity to Organizational Productivity” - Using SharePoint, people can set up their Web sites to share information with others, manage documents from start to finish, and publish reports to help everyone make better decisions.
SharePoint is a content management system build with an ASP.NET front end, and an XML based back end running on IIS and SQL Server as back end. SharePoint acts as the single platform to share, communicate, store, and collaborate the content, documents, and records.
The companies are going for SharePoint due to the following reasons:-
Integration with Cloud
Content Management.
Internet & Intranet Portals.
Easy Migration.
Integration with CRM, TFS, Office etc.,

3. History of SharePoint Versions
SPS 2001
STS (WSS v1)
ASP
32 bit
SPS 2003
WSSv2
MOSS 2003
.NET 2.0
CMS 2002
MOSS 2007
WSSv3
.NET 3.0 (Used WF)
VS 2005/2008
32 bit and 64 bit
SPS 2010
SP Foundation 2010
SP Server 2010
.NET 3.5
VS 2010
64 bit only
SPS 2013
SP Foundation 2013
SP Server 2013
.NET 4.5
VS 2012
Year
Core Infrastructure Product
Business Value Product
2001
SharePoint Team Services
SharePoint Portal Server 2001
2003
Windows SharePoint Services 2.0
Microsoft SharePoint Portal Server 2003
2007
Windows SharePoint Services 3.0
Microsoft Office SharePoint Server 2007
2010
Microsoft SharePoint Foundation 2010
Microsoft SharePoint Server 2010
2013
Microsoft SharePoint Foundation 2013
Microsoft SharePoint Server 2013

4. SharePoint 2013 Editions – On Premise
SharePoint Foundation is built on .NET Framework 3.5, ASP.NET 3.5, IIS, SQL Server 2008
SharePoint Foundation
SharePoint Server Standard
SharePoint Enterprise
List, Libraries, Content types and Field types
Site Templates & Definitions
Client Object Model
Web Pages
Web Parts
Workflows
Business connectivity Services (BCS)
Security, Claims & Identity
Sandbox Solutions
Power Shell
Service Application Framework
Mobile Pages & Web Part Adapters
Enterprise Content Management
Web Content Management
Enterprise Search
Word Automation Services
Social Data & User Profiles
Dashboards
InfoPath Form Services
Visio Services
Excel Services
Access Services
Performance Point Services

5. SharePoint 2013 Wheel (Capabilities)
Sites : Different types of sites available for use and features within the sites.
Communities: Communities and Social features such as blogs and Wikis
Content: Core enterprise content management features
Search: Search driven features
Insights: Business Intelligence features such as KPI
Composites: Ability to integrate external applications using BCS

6. SharePoint 2010 Wheel (Capabilities)

7. SharePoint Vision
HR, Finance, etc.
Team Collaboration
Personal
Enterprise Portal
Internet Presence
Customers
Partners
Employees
Business Applications
(SAP, data warehouse, custom . . .)
XML Web Services
To handle the SharePoint Requirement either by using Outbox (OOTB), Customization, Configuration
A unified, enterprise-ready solution that boosts organizational effectiveness by:
making information and knowledge sharing intuitive and easy
controlling and reusing content while reducing information management risk
enabling faster and more insightful decision making

8. Flavors of SharePoint 2013 SharePoint 2013 On-Premise On Cloud
(No hassles of installation or deployment )
Cloud: “computing capability delivered as a utility through Internet standards and protocols”
IaaS – Infrastructure as a Service, virtualized and hosted server resources
PaaS – Platform as a Service, app dev in the cloud, NAPA, SQL Azure
SaaS – Software as a Service; e.g. O365, SkyDrive, Hotmail
Providers include Microsoft Azure, Microsoft Office 365, Amazon Web Services, Google App Engine, Force.com
Azure – Microsoft Public Cloud (IaaS and PaaS)
Office 365 – Exchange, LYNC, SharePoint and Office (SaaS)
NAPA –browser-based code editor to build Apps for Word, Excel, Outlook, Project and SharePoint; hosted in Windows Azure
REST - Representational State Transfer is intended to evoke an image of how a well-designed Web application behaves
OAuth - OAuth is an open protocol for authorization. OAuth enables secure authorization from desktop and web applications in a simple and standard way.
OData - Open Data Protocol (OData) is a web protocol for querying and updating data using web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON
Foundation
Enterprise
Other providers like Amazon Web Services,
Rackspace
running SP on VMs in the cloud through Windows Azure or Amazon Web Services and have all the capabilities
Standard
SharePoint Online, Office 365
Lacks the full set of features available in SharePoint
No full trust Solutions
No access to central admin
No usage reporting
No PPS
No SSRS (integrated mode)
No PowerPivot
No Site collections greater than 100GB
No way(yet) to get back data on-premise, once it goes on-line

9. SharePoint 2013 Technology Stack
Requires all-x64 bit environment
Microsoft SharePoint Server 2013
Microsoft SharePoint Foundation 2013
.NET Framework and ASP.NET 4.5
Internet Information Services 7.5
SQL Server 2008 R2 / 2012
Windows Server 2008 (x64 only)
Windows Server 2012(x64 only)

10. Server Roles & Elements in a SharePoint Farm
Front End Web Server (SharePoint IIS 7.5 Installed)
A Web front-end server runs IIS7.5 and is contacted by clients when they access SharePoint sites. No data is stored on Web front-end servers.
Application Server (SharePoint Installed )
Application servers host services such as indexing, Search, or Office Excel calculation services.
Database Servers (SQL Server R2 / 2012)
The database server hosts the content and configuration databases used by Office SharePoint Server 2013.
SharePoint Farm
Web Application
Site Collection
Site
List/Document library
Content Item

11. SharePoint 2013 Architecture

12. Logical Architecture ADFS SharePoint 2013 Farm
Directory – AD DS
Authentication – Claim based Authentication – Default
ADFS
Users
Load Balancer
Request Management
SharePoint 2013 Farm
External Systems
Application Pool 9
Request Management: Request Management feature in SharePoint 2013 manages incoming requests by evaluating logic rules against the user requests in order to determine what/which action to take, and which machine or machines (Targets) in the farm should handle the requests.
Evaluation is done using the below parameter:
A Constant Static weight can be assigned by the administrator to determine powerful and weak servers
A dynamic Health weight which is assigned by Health Analysis through system with a score from 0 (Good) to 10(Very poor).
Authentication: SharePoint 2013 supports two authentication types for user authentication:
Claims-based authentication
Windows classic mode authentication
The result of a claims-based authentication is a claims-based security token, which the SharePoint Security Token Service (STS) generates. The result of a Windows classic mode authentication is a Windows security token. We recommend that you use claims-based authentication for user authentication.
SharePoint 2013 supports Windows, forms-based, and Security Assertion Markup Language (SAML)-based claims authentication
App Authentication: App authentication is the validation of a remote SharePoint app's identity and the authorization of the app and an associated user of a secured SharePoint resource request. App authentication occurs when an external component of a SharePoint Store app or an App Catalog app, such as a web server that is located on the intranet or the Internet, attempts to access a secured SharePoint resource.
Server to Server (S2S) High Trust Authentication is used for Authenticating Remote Apps with SharePoint.
Distributed Cache service:
The Distributed Cache service provides caching functionality to features in SharePoint Server The Distributed Cache service is either required by or improves performance of the following features
Authentication
Newsfeeds
OneNote client access
Security Trimming
Page load performance
Application Management Service: The App Management service application is largely responsible for licensing information, for example its database is accessed each time an app is used to verify the validity of the request.
Work Management Service: The Work Management Service Application provides functionality to aggregate tasks to a central location.
Users get the possibility to view and track their to-dos and tasks.
Tasks can be cached to a users personal site.
Tasks can be aggregated from Exchange, Project Server and SharePoint.
Machine translation service: Machine Translation Service is a new service application in SharePoint 2013 that provides automatic machine translation of files and sites. When the Machine Translation Service application processes a translation request, it forwards the request to a cloud-hosted machine translation service, where the actual translation work is performed.
Office Web Apps: With SharePoint 2013 the server part to edit/view Office documents with the browser is now a separate product and needs to be also installed separately
Lync Server: With Lync Server 2013 deployed in an organization with Exchange 2013, you can configure Lync to archive instant messaging and on-line meeting content such as shared presentations or documents in the user’s Exchange 2013 mailbox
Application Pool 1
Published Intranet KM Portal
Central
Administration
Document
Conversions
Line of Business Applications
Work
mgmt
Services
Claims to
Windows
Token
Distributed
Cache
WFE 1
WFE 2
WFE 3
Content DB:
200 GB
Application Pool 2
Application Pool 3
ASP.NET Application
(Provider Hosted –
FARM Solution)
Application Pool 10
Excel
Services
InfoPath Form
Services
Word
Services
Collaboration Portal – Team Sites
App 1
App 2
App 3
S2S High Trust
Web Application
PowerPoint
Visio Graphic
Services
Access
Services
Content DB:
200 GB
Application Pool 4
Application Pool 11
App Mgmt.
Service
Machine
Translation
Crawl DB
Web Application – My Site
Application Pool 5
Application Pool 6
Application Pool 7
Lync Server 2013
(Meetings, Audio, Video etc.)
User profile
Managed
Metadata
Search
DBServer
Crawl DB And
Other SharePoint DBs
2 SQL Clustered/
Mirrored DB servers
Content Logs: 100 GB
Temp DB: 100 GB
Content DB:
200 GB
Workflow Manager (SharePoint 2013 Workflow Platform)
Application Pool 8
Application Pool 8
BCS
Secure Store
Services
Static
Service
Application Pool 12
Office Web Application Server
Web App – Search Center

13. Logical Architecture Logical Architecture Server Farms
Service Applications
Application Pools
Logical Architecture
Content Database
Zone
Web Applications
Site Collections
Sites
Lists & Libraries

14. Logical Architecture

15. Physical Architecture
Farm Model
RAM (Per Server)
CPU (Per Server)
Single Server
24 GB
4 Cores
Small Farm
1 x WEB/APP + SQL
16 GB WEB/APP
16 GB SQL
4-8 Cores
Medium Farm
2 WEB APP + SQL
16 GB WEB
16 GB APP
32 GB SQL
Large Farm
2-3 WEB APP + SQL

16. Hardware Requirements
Web servers, application servers, and single server installations
Installation Scenario
Deployment type and scale
RAM
Processor
Hard Disk space
Single server with a built-in database or single server that uses SQL Server
Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 with the minimum recommended services for development environments.
8 GB
64-bit, 4 cores
80 GB for system drive
Development or evaluation installation of SharePoint Server 2013 or SharePoint Foundation 2013 running Visual Studio 2012 and the minimum recommended services for development environments
10 GB
Development or evaluation installation of SharePoint Server 2013 running all available services.
24 GB
Web server or application server in a three-tier farm
Pilot, user acceptance test, or production deployment of SharePoint Server 2013 or SharePoint Foundation 2013
12 GB

17. Hardware Requirements
Database Servers
Component
Minimum requirement
Processor
64-bit, 4 cores for small deployments (fewer than 1,000 users)
64-bit, 8 cores for medium deployments (between 1,000 to 10,000 users)
RAM
8 GB for small deployments (fewer than 1,000 users)
16 GB for medium deployments (between 1,000 to 10,000 users)
Hard disk
80 GB for system drive
Hard disk space depends on how much content that you have in your deployment

18. Software Requirements
SharePoint 2013 Prerequisite
Microsoft .NET Framework 4.5
Windows Management Framework 3.0
Microsoft SQL Server 2008 R2 SP1 Native Client
Windows Identity Foundation (KB974405)
Windows Identity Extensions
Microsoft Sync Framework Runtime v1.0 SP1 (x64)
Windows Server AppFabric
Microsoft Information Protection and Control Client
Microsoft WCF Data Services 5.0
Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB
SharePoint 2013 Edition
SharePoint Server 2013 Standard/Enterprise Edition

19. Topology
Supported Topologies – Limited Deployments

20. Topology - Small Multi Purpose
Four Server Farm

21. Topology – Medium Farm
Six Server Farm

22. Topology - Medium Farm + Office Web Apps
Six Server Farm

23. Topology - Large
Large Farm

24. Topology - Hybrid
Hybrid Farm

25. Topology
Stretched Farm

26. SharePoint 2013 Architecture
In general model has stayed same as in previous version
Numerous platform level improvements and new capabilities
Shredded Storage
SQL Improvements
Cache Service
Request Management
Themes
Sharing

27. New in SharePoint 2013 – Contd..
Distributed Cache Service: The Distributed Cache service provides caching features in SharePoint Server The improved social features in SharePoint 2013 can generate dramatic amounts of new, frequently changing content in a large organization. When you couple this with the content in SharePoint, this could cause an awful lot more database access and page slowdown
The microblog features and feeds rely on the Distributed Cache to store data for very fast retrieval across all entities. The Distributed Cache service is built on Windows Server AppFabric, which implements the AppFabric Caching service. Windows Server AppFabric installs with the prerequisites for SharePoint Server 2013.
The Distributed Cache service is either required by or improves performance of the following features:
Authentication
Newsfeeds
OneNote client access
Security Trimming
Page load performance

28. New in SharePoint 2013 – Contd..
Request Management: helps the farm manage incoming requests by evaluating logic rules against them in order to determine which action to take, and which machine or machines in the farm (if any) should handle the requests. Request Management enables “advanced” routing and throttling. Example behaviors include:
Route requests to Web Servers with a good health score, preventing impact on lower health Web Servers
Prioritize important requests (e.g. end user traffic) by throttling other types of requests (e.g. crawlers)
Route requests to Web Servers based upon HTTP elements such as host name, or client IP Address
Route traffic to specific servers based on type (e.g. Search, Client Applications)
Identify and block harmful requests so the Web Servers never process them
Route heavy requests to Web Servers with more resources
Allow for easier troubleshooting by routing to specific machines experiencing problems and/or from particular client computers
The Request Management service instance is provisioned on every Web Server in the farm
Request Management is scoped and configured on a per Web Application basis, for each Web Application configured
The Request Manager configuration includes five key elements which dictate how rule logic is evaluated and applied before requests are routed and to which servers they are routed.
Routing Targets (Servers) (has a Static Weighting - constant and Health Weighting which is dynamic and evaluated from the Health Score (0 to 10)
Machine Pool (collection of routing targets)
Routing Rules -definition of the criteria to evaluate before routing requests which match the criteria
Throttling Rules - definition of the criteria to evaluate before refusing requests which match the criteria
Execution Groups - collection of Routing Rules which allows the precedence of rule evaluation

29. New in SharePoint - Remote Event Receivers
In SharePoint 2013, a new concept, Remote Event Receivers, has been introduced, where the event generated by a SharePoint app could be listened to and handled by the SharePoint Server.
We could create SharePoint Apps (that is a standalone module of code that is complete in itself and can be installed / uninstalled independently on a Client) that can act as event generators. The handlers can be written using web services. These are very similar to the event receivers in the earlier version - except that these work in remote clients.
Instead of running code on the SP server, the app fires an event that is handled by a web service. By registering a remote end-point we can invoke either a one-way or two-way event receiver.
Visual Studio 2012 provides templates to create a Remote Event Receiver, that creates the skeleton for this set up, that we can build on, to meet our requirements. By default, when we use Visual Studio 2012 to create the remote event receiver, there are 2 methods in the WCF service; they are:
ProcessEvent() that handles events that occur before an action occurs, such as when a user adds or deletes a list item. This is a synchronous event (2-way that can handle "-ing" (current) events) that can call-back to SharePoint, for example cancelling an addition to a list
ProcessOneWayEvent() that handles events that occur after an action occurs, such as after a user adds an item to a list or deletes an item from a list. This is an asynchronous event (1-way that can handle "-ed" (past) events, fire and forget type)
Event receivers in earlier versions of SharePoint primarily ran on the SharePoint Server to handle events that occurred on SharePoint objects such as list, libraries, site etc.

30. Authentication Modes
SharePoint 2013 continues to offer support for both claims and classic authentication modes
However claims authentication is the default authentication option now
Classic authentication mode is still there, but can only be managed in PowerShell – it’s gone from the UI
Support for classic mode is deprecated and will go away in a future release, so recommend moving to Claims
There also a new process to migrate accounts from Windows classic to Windows claims

31. Authentication in SharePoint 2013
Authentication for in SharePoint 2013
Unchanged for calls to standard SharePoint sites
For app webs, calls are internally authenticated with app identity
In remote calls, apps are authenticated using app-specific security tokens
Security tokens can contain both app and user identity or just app identities
Requirements for establishing SharePoint app identity
Host Web application must be claims based
Incoming calls must target CSOM/REST endpoints
Supported CSOM/REST endpoints are not extensible

32. SharePoint 2013 Licensing SharePoint Online
SharePoint Online as a standalone plan or included as part of Office 365 plans.
For On-Premises
Intranet sites are licensed using a Server/CAL (Client Access License) model. SharePoint Server 2013 is required for each running instance of the software, and CALs are required for each person or device accessing a SharePoint Server.
SharePoint Standard CAL
The Standard CAL delivers the core capabilities of SharePoint
Sites: A Single Infrastructure for All Your Business Web Sites
Communities: An Integrated Collaboration Platform
Content: ECM for the Masses
Search: Relevance, Refinement, and People; includes FAST Enterprise Search
SharePoint Enterprise CAL
The Enterprise CAL delivers the full capabilities of SharePoint . Include Standard CAL features +
Business Solutions (includes Access Services and InfoPath Services)
Business Intelligence for Everyone (includes Power View, PerformancePoint Services, Excel Services, and Visio Services)

33. Browser Support Matrix
Supported
Not supported
Internet Explorer 11 X
Internet Explorer 10
Internet Explorer 9
Internet Explorer 8
Internet Explorer 7
Internet Explorer 6
Google Chrome (latest released version)
Mozilla Firefox (latest released version)
Apple Safari (latest released version)
Mobile device OS
OS version
Browser
Smartphone device
Slate or tablet device
Windows Phone
Windows Phone 7.5 or later
IE Mobile
Supported
Not applicable
iOS
5.0 or later versions. Video play experience requires iOS version 6.0 or later.
Office Web Apps full functionality is supported on iPad versions 2 and 3 using iOS 6.0 or later versions. Limited viewing and editing functionality is also supported on iPad versions 1, 2, 3 using iOS version 5.1
Safari
Android
4.0 or later versions. Video play experience requires Android version 4.1 or later.

34. Platform level Improvements in SP 2013
Minimal Download strategy (MDS) UX - reduces the amount of data that the browser has to download when users navigate from one page to another in a SharePoint site by processing only the differences (or delta) between the current page and the requested page. Site has the page in the URL followed by a hash mark (#) and the relative URL of the requested resource.
Shredded Storage - the documents are broken down into pieces and stored as XML only changes in the new version are stored in the DB instead of the entire document
Push Notification - SP can send alerts/ SMS to applications on mobile devices that have subscribed to alerts in a site
End user licensing model - organizations can have fixed number of “Enterprise” and “Standard” CALs for the same farm to cut costs. Some users may only need standard license ( depending on the features they need to use) and others may need enterprise license. Earlier, in SP 2010, the org had to choose among one of these only for the entire farm
Geo Location Field - enables annotation in SharePoint lists with location information
SharePoint 2013 works with no Active X controls, so supports any modern browser.
When users browse an MDS-enabled site, the client processes only the differences (or delta) between the current page and the requested page. You can identify a site that has MDS enabled by looking at the URL. An MDS-enabled site has the (3) _layouts/15/start.aspx page in the URL followed by a hash mark (#) and the relative URL of the requested resource.
The main components of MDS are two engines, one in the server and another in the client, that work together to calculate the changes and render the pages in the browser when the user navigates from page to page in the site.
in some situations it’s not possible to determine whether the page can be updated properly. In these situations, the MDS engine issues a failover, which consists of an extra round trip to redirect the browser to the full version of the new page. These are the most common reasons why failover occurs:
The new page has a different master page.
The current master page has changed.
The MDS engine detects non-compliant HTML, for example:
Pages using ASP.NET 2.0
CSS or scripts not registered in the MDS engine
Illegal HTML
There are non-compliant controls on the page, for example:
The control is not in the MDS engine whitelist.
The control assembly is not marked as compliant.
The control class doesn’t have the MDS attribute.

35. Workflow Manager in SharePoint 2013
Uses ‘Windows Azure Workflows’
Workflows now run as a separate service to SharePoint itself, and can be hosted on-premise or externally (similar to App Model).
Fully Declarative Workflows
REST based messaging, Scalability
Activity Management, Tracking and Monitoring
Instance Management
Ability to call external web-services in the workflow
Loops in workflows are possible
Ability to recall – approval workflow
Whereas in previous versions workflow execution was hosted in SharePoint itself, this has changed in SharePoint Workflow Manager Client 1.0 is external to SharePoint and communicates using common protocols over the Windows Azure service bus, mediated by Oauth
Workflow Manager Client 1.0 is represented in SharePoint 2013 in the form of the Workflow Manager Client 1.0 Service Application Proxy. This component allows SharePoint to communicate and interact with the Workflow Manager Client 1.0 server. Server-to-server authentication is provided using OAuth.
SharePoint events for which a workflow is listening, like itemCreated, itemUpdated, and so on, are routed to Workflow Manager Client 1.0 using the Windows Azure service bus. For the return trip, the platform uses the SharePoint Representational State Transfer (REST) API to call back into SharePoint.

36. New Workflow architecture - Advantages
Windows Azure Workflow is built on Windows Workflow Foundation 4.5 (WF4.5). This will require a separate install that can run on a SharePoint server or its own environment.
By taking workflow processing out of SharePoint and creating a Workflow “farm,” several improvements become available.
The SharePoint farm(s) now have less processing to do. The WAW environment will manage the workload and update SharePoint via web service connections. SharePoint has plenty of loads to manage and SharePoint 2013 introduces multiple features that are, or can be, offloaded to other environments outside of SharePoint.
It’ll help simplify the upgrade process to the next version of SharePoint.
The ability to use WAW for multi- and cross-platform workflow. This will allow you to host all your .NET workflows, regardless of if they’re SharePoint, for Windows applications, or Web applications. There’s also the ability to reuse the same workflow for multiple platforms.
Windows Azure Workflow, despite its name, can be hosted on premises.

37. Solution Architecture Overview
Multi Languages
Presentation Layer:- Responsive web layouts- HTML5 CSS3
Social Computing: The social computing and collaboration features in SharePoint Server 2013 offer an improved administration and user experience, in addition to new functionality for enterprise users to share and collaborate with others in their organization.
The introduction of Community Sites offers a forum experience to categorize discussions around subject areas, and connect users who have knowledge or seek knowledge about subject areas. Improvements to My Sites offer a more intuitive workflow for users to develop their personal profiles, store content, and keep up-to-date with activities of interest.
App Model: SharePoint applications no longer need to live in SharePoint
Custom code executes in the cloud or client
Apps have no custom code that runs on the SharePoint servers
Apps can be granted permissions
Apps communicate with SharePoint using REST / CSOM and Oauth
Apps can be acquired via a centralized marketplace
Corporate marketplace
Public marketplace
APIs for manual deployment
Extended Cloud Support:
Apps have no custom code that runs on the SharePoint servers. Instead, all custom logic moves "up" to the cloud or "down" to client computers.
Machine Translation using the Microsoft Translator service present in the cloud.
Provides supports workflow execution on Cloud or on-Premise through Workflow Manager Service
Mobility:
With SharePoint 2013, you can combine Windows Phone 7 applications with on-premises SharePoint services and applications, or with remote SharePoint services and applications that run in the cloud (such as those that use SharePoint Online), to create powerful applications that extend functionality beyond the traditional desktop or laptop and into a truly portable and much more accessible environment. The new mobility features in SharePoint 2013 are built on existing Microsoft tools and technologies, such as SharePoint, Windows Phone 7, Visual Studio, and Microsoft Silverlight. You can create SharePoint-powered mobile applications for Windows Phone using the new SharePoint phone application wizard template in Visual Studio, which lets you create simple list-based mobile applications. You can integrate new features introduced in SharePoint 2013, such as the Geolocation field type and “push" notifications from SharePoint Server, into your mobile applications
Support for Open Standards:
SharePoint 2013 makes it easy for any web developer, including those who work on non-Microsoft platform stacks, to create SharePoint solutions. What makes this possible is that SharePoint 2013 is based on common web standards like HTML, CSS, and JavaScript. Furthermore, implementation relies on established protocols like the Open Data protocol (OData), and OAuth
Unified Search:
FAST Search Engine and SharePoint Enterprise Search have been combined in SharePoint 2013.
Search functionality in SharePoint 2013 includes several enhancements, custom content processing with the Content Enrichment web service, and a new framework for presenting search result types. Additionally, there have been significant enhancements made to the keyword query language (KQL).
Secure Access Gateway
Authentication
Integrate
Web Server
Application Server
SharePoint Portal Components
Line of Business
METRO Style UI
Social Collaboration
The New App Model for SharePoint and Office
Extended Cloud Support
Integration
Connectors
Mobility – Multi Device, Multi Channel
Considerable support for Open Standards
Unified Search Experience
Workflows
Design Manager
Enterprise Content Management
Web Content Management
SharePoint 2013 Platform
Third Party Tools
(Administration, Monitoring,
Development & Code control)
Design Tools
(SP Designer)
Development Tools (Visual Studio 2012)
External Systems

38. Microsoft SharePoint Server 2013
Service applications in SharePoint 2013
New service applications available and improvements on existing ones Office Web Apps is no longer a service application Web Analytics is no longer service application, it’s part of search
App Management Service – manage apps for SharePoint
Machine Translation Service – manages translation services
Work Management Service – aggregates tasks
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.

39. Architecture Changes – Service Applications
Translation service
Sites
OOB
Access Services
SharePoint Front End
App Store
Licenses
Application management service
Document
SP Designer
Purchases
Streams
SQL Server Storage
App URL
Visual Studio
Workflows
Enables App creation
for running business
Multi-lingual
Infrastructure Enabler for New SP Apps
New Services
Existing/Changed Services
Discontinued
Services
MMS
Visio
Enhanced Excel Services
User profiles
Enhanced Powerpoint Services
Office Web Apps Service
Unified
Search
Services
BCS
3rd Party Services
Web Analytics
Portal

40. New Service Applications in SP 2013
Features / Changes
App Management Service App – New
(available in SharePoint Foundation 2013 and SharePoint Server 2013)
Is responsible for storing and providing information concerning SP App licenses and permissions
All licenses for apps downloaded from Marketplace will be stored in Apps service application
Accessed each time app is requested or used in SharePoint to verify validity of the request
SharePoint Translation Service–
(available only in SharePoint Server 2013 Std & Ent)
Provides built-in machine translation capabilities on the SharePoint platform to translate documents(MS Word), pages and sites into different languages
Cloud-hosted machine translation services
Translations can be synchronous(translated as soon as they are submitted – manual request) or asynchronous(translation request is triggered by a timer job- automated)
Extensible with support for Full trust solutions and SP Apps, REST API, CSOM and APIs for batch and immediate translations
Translation process have been integrated to variations
External/Manual translation providers can also be leveraged by using XLIFF files- the standard used by translation vendors
PowerPoint Conversion Service Application – (with SharePoint Server 2013 – Std & Ent only)
PowerPoint Automation Services is about file conversions – such as ppt to pptx, pdf, xps, jpg, png aimed at converting for distribution to clients without Microsoft PowerPoint or to prevent the presentation from being edited
API very similar to Word Automation Services
Work management Service Application –
(available only in SharePoint Server 2013 – Std & Ent)
Work management Service applications provides functionality to aggregate tasks to central place so that users can view and track their work and to-dos
Tasks cached to person’s my site with tasks from Exchange, Project Server and SharePoint
Implementation is based on provider model, so that additional systems maybe integrated to same architecture in future

41. Improved Service Applications in SP 2013
Features / Changes
Business Data Connectivity service
(available in Foundation & Server Versions)
OData Support as data source along with those supported in SharePoint 2010
Eventing FrameWork for external notifications ( even for external lists)
Supports SharePoint Apps as BDC models
External list enhancements include Performance improvements, Data Source Filtering, Sorting, Export to Excel
User profile service
(available only in Std & Ent)
Performance improvement that claims to reduce full import time from up to 2 weeks down to 60 hours for extremely large directories – for example, 200K users and 600K groups aimed at direct AD forest import;
Word automation service
(available only in SharePoint Server 2013 – Std & Ent)
Word Automation Services is all about file conversions – such as doc to docx, pdf, updating the Table of Contents, the Table of Authorities, and index fields, recalculating all field types, Setting the compatibility mode of the document to the latest version or to previous versions of Word etc
On-demand file operation requests to Word Automation Services that are processed immediately and have higher priority than traditional asynchronous Timer Job-based requests and notify or update items in SharePoint after completion. Overcomes the pain points in SP 2010 of waiting until timer job executes for file generation and not knowing when conversion has been completed.
Access Services App Databases
(available only in SharePoint Server Enterprise 2013)
Collaborative web applications on SharePoint & SQL Server, Site as SharePoint App
Database is a single SQL Server database - Tables in Access are tables in SQL. Access tables converted to SQL Tables behind the scenes. Access is an abstraction layer over SQL Server
Simplified designers. Developer-level experience not required. Provides capability for creating data tracking applications easily as business users
Access "15 storage based on SQL 2012 or SQL Azure
Provides more scalable data storage platform and Rapid Application Development (RAD)
Access Services 2010 – was primarily meant to share Access databases in SharePoint. Here in 2013, the database is actually converted to SQL tables and stored in SQL.
Visio Graphics Services
Visualize diagrams in browser
Support for Microsoft Visio 2013 file format(.vsdx), Microsoft Business Connectivity Services (BCS) data sources
New commenting framework that provides programmatic access to comments. Users can add comments to a Visio Drawing collaboratively on the web via Visio Services in full page rendering mode.Comments are embedded to actual visio file – Available in client as well
We can now create a SharePoint Workflow using Visio. After the business logic is complete, the workflow can be exported to SharePoint Designer and can be wired up to a SharePoint site
Excel Service
Powerful analytics with the PowerPivot add-in with support for integration with SSAS, SQL Server, OLEDB, ODBC data sources
Quick explore to drill up and down to view higher or lower levels of information. To create new views using Quick Explore , we must use Excel Client
Touch and Device Support on iOS, Android and Microsoft platforms
Excel Interactive View creates an Excel table that is based on an HTML table that is hosted on the same webpage. When you place the Excel Interactive View HTML tag above an HTML table on a hosted webpage, the tag reads the data in the HTML table and creates an Excel table in the browser that you can interact with (filter, sort) and create charts.
OData support through REST APIs
One deprecated is that we can't edit workbooks in the browser that have external data connections in SharePoint 2013

42. Enterprise Content Management in SharePoint 2013

43. Enterprise Content Management in SharePoint 2013

44. Web Content Management in SharePoint 2013

45. Search in SharePoint 2013 Highly Configurable
New Search architecture with one unified search
Personalized search results based on search history
Rich contextual previews
FAST features merged (in general) into SharePoint Search
Better Ranking Models
Customizable query spell correction dictionaries
Highly configurable Query Rules (New)
Rich Search Analytics
Rich Thumbnail Previews
Preview entire document inside search results
Term Store based faceted refinements (Logical Taxonomy Search)
For Camera term, you can add refiners for Megapixel Count and Manufacturer
Different refinements can be made to render differently
Highly Configurable

46. Search in SharePoint 2013 - Search (FAST Integrated)
Significant improvements in user experience.
Visual display of contents as you hover in search results.
Best bets now called Promoted Results.
Search remembers what you have previously searched and clicked and displays these values as query suggestions at the top of the results page.
Results show number of times a document has been viewed.
Results pages allows you to page through PowerPoint presentations without leaving the search results page.
One click to “view in library.”

47. Social Enhancements in SharePoint 2013

48. Social Enhancements in SharePoint 2013..

49. Social in SharePoint 2013 - Communities

50. Social in SharePoint 2013 - Communities
Access very different from team sites –users can observe conversations and then “join” a community when they want to post.
Community can allow anyone to join or can require approval by a Moderator before allowing someone to become a “Member.”
Becoming a member means you are automatically “Following” the community site.
Member photos show up next to all posts.
“Gamification” options to encourage participation –points, badges, and a “top contributors” leader board.
Designated users can be “gifted” a badge –to identify someone as an “Expert” or “Thought Leader” so that discussion participants can easily distinguish contributions.
Ability to categorize conversations by topic with an image –to create a welcoming environment and encourage interaction

51. Social Computing in SharePoint 2013
Each user has a Newsfeed that is similar to a Facebook activity stream.
See stream of the entire organization or filter based on topics and people you are following.
Post or reply in the stream and #hash tags.
Activity posts are saved for as long as you decide to retain them (most organizations align this policy with retention) and are searchable.
Follow #Hash tags to get notified when new content relevant to your area of interest is added.
@mention someone to direct an activity post to their attention (as in Twitter).

52. Social Enhancements in SharePoint 2013..
Task Aggregation: Single, aggregated, view of all user tasks across SharePoint Sites, Project Sites and Exchange

53. BI in SharePoint 2013

54. BI in SharePoint 2013

55. PowerPoint Automation Services
PowerPoint Automation Services is a new service application in SharePoint Server 2013 that provides automatic server-side conversion of PowerPoint Presentations from one format to another, for example, a PowerPoint Presentation in Open XML File Format - .pptx format can be converted into Portable Document Format (.pdf) for archival purposes, distribution to clients who do not have Microsoft PowerPoint installed, or to protect the presentation from editing
PowerPoint Automation Services supports conversion of Open XML File Format (.pptx) and PowerPoint presentation format (.ppt) to .pptx, .pdf, .xps, .jpg, and .png.

56. Self-service BI
PowerPivot data is an analytical data model that you build in Excel using the PowerPivot for Excel add-in.
PowerPivot for SharePoint 2013 provides server hosting of PowerPivot data in a SharePoint 2013 farm. Server hosting of that data requires SharePoint 2013, Excel Services
Data is loaded on PowerPivot for SharePoint instances in the farm, where it can be refreshed at scheduled intervals using the PowerPivot data refresh capability that the server provides
PowerPivot allows us to import millions of rows from multiple data sources, providing business users the capability to create mash-ups and analyze data and create analytical models. In Excel 2013 this is built in, in 2010 this requires installing an add-in.
PowerPivot allows you to get data from, SQL Database, Microsoft Azure, Azure Data Marketplace, DB2, Text files, Oracle, and practically any OLEDB or ODBC provider.
Using the data we can generate pivot tables and charts, as well as add slicers which users can use to see data in different ways.
Since its excel, business users can use their knowledge to manipulate the data and views to suit there needs and generate insightful charts and visualizations. Once we have the Excel workbook ready we can upload it to SharePoint and expose it through Excel Web Services.
With Excel Services in SharePoint, site visitors are able to view and interact with Excel workbooks that have been published to SharePoint sites. Business users can create a dashboard experience which allows site visitors to explore data and conduct analysis in a browser window.
Key advantages of self-service Business Intelligence:
Low investment
Less reliance on I.T
Collaboration

57. Mobile in SharePoint 2013

58. Gone in SharePoint 2013 Sandboxed Solutions
Classic Mode Authentication
Chart web part
Status Indicators
XSLT replaced by Display Templates
SkyDrive Pro instead of My Sites
Web Analytics / Statistics
Design view in SharePoint designer
Visual Upgrade – replaced by Deferred site collection upgrade

59. Customization packaging and deployment options
Farm
Sandbox
SP Apps
Full trust solutions
Customizations to file system of servers
Classic model from 2007
Declarative elements
Partially trusted code service still included for limited server side support
New Apps model
Deployed from corporate catalog or office market place
Manage permission and licenses specifically
Preferred option

60. SharePoint 2013 Development Roadmap
Build server-side farm solutions that extend core SharePoint capabilities
Flexible development model to create apps for SharePoint that take advantage of standard web technologies, such as JavaScript, OAuth, and OData
SharePoint 2013 provides you with functionality to interact with SharePoint resources and a wide range of hosting options
The new app for SharePoint development model gives you the ability to build apps that take advantage of SharePoint capabilities and that run in the cloud instead of on your SharePoint farm
Client Side Programming is encouraged

61. Intro to Apps Drawbacks of SharePoint solutions (farm, sandboxed):
Custom code runs inside the SharePoint Environment
Poses security risks and affects scalability
Root cause of most SharePoint outages / issues
Lots to deploy
Not possible in hosted environments
Requires a big server touch
Custom code has dependencies on SharePoint dll’s
Makes migration difficult
Permission model is very rigid and difficult to customize
Permissions cannot be configured for the solution itself very easily
Impersonation has it’s own issues
Hard to manage
No support for upgrades and easy distribution and installation
Developers must know SharePoint API
Custom Code on Server
Root cause of most SharePoint outages / issues
Lots to deploy
Not possible in hosted environments
Requires a big server touch
Sandbox
Limited set of things you can do
In both, developers must know SharePoint API

62. The New App Model
SharePoint applications no longer need to live in SharePoint
Custom code executes in the cloud or client
Apps can be granted permissions
Apps communicate with SharePoint using REST / CSOM and Oauth
Apps can be acquired via a centralized marketplace
Corporate marketplace
Public marketplace
APIs for manual deployment
Benefits:
No custom code on the SharePoint Server
Easier to upgrade
Works in hosted environments without limitations
Reduces the time for building these applications
Don’t need to be familiar with SharePoint APIs and concepts
Versatility
Allows you to use frameworks, languages, platforms that are not supported by SharePoint

63. Host Web App Web Host Web and App Web
Installation of App creates child site in target site
Host Web is the site into which the app is installed
App Web is created by SharePoint automatically when the app is installed
App Web provides scope for private implementation details
App Web can add declarative items to the App Web such as Lists, Pages, CSS, JS Files etc.
Host Web
App Web

64. SharePoint Apps – Deployment Models
SharePoint-hosted - App and all resources will be hosted in your SharePoint farm. Used for light weight  smaller applications using HTML, Java Script and Client object model. Here you do not need to write server-side code. scope is site collection level.
Auto hosted - App is hosted in cloud. Used for light weight applications but the code is deployed at windows azure using cloud. scope is at site level.
Provider-hosted - App and all resources are hosted on separate server. Code does not exists on SharePoint but will be in other domain which can be windows azure, IIS or even PHP app from your domain server. 

65. Apps - Continued SharePoint-Hosted Auto-Hosted Provider-Hosted
A way to deploy client-side, lightweight apps to SharePoint 2013 (HTML / Javascript)
No Server-side Code
Static Application files / pages that reside on SharePoint instance
Good choice for apps such as branded list views, media apps, weather apps
Sphosted apps - Typically used to use SharePoint elements such as Lists, Content Types, Actions etc.
Auto-Hosted
Code is seamlessly deployed to Windows Azure in the background – so SharePoint automatically creates the cloud-hosted app for us
Code is deployed to a special Office365 Windows Azure instance and registered as an authenticated and authorized app with SharePoint
We don’t have complete access to the entire platform capabilities of Windows Azure platform; however, we have enough to build interesting applications – leverage Windows Azure web sites and Windows Azure SQL DB
Provider-Hosted
Richer and more flexible
Code runs in a different domain – often framed in the context of cloud deployment
External server doesn’t necessarily need to be a Windows Server – based application; we could be running a PHP app on a Linux / Apache server
Yammer is an example of a Provider-hosted app

66. SharePoint Solutions & apps

67. Hosting : Cloud v/s SharePoint
Cloud Hosted
SharePoint Hosted
Preferred hosting model for almost all types of apps
Good for smaller apps and recourse storage
Full power of the web, infrastructure and technology
Limited : No server-side code allowed
Requires a separate hosting environment to be set up
Hosted within your SharePoint farm
Additional administration and management effort involved
Managed as part of your SharePoint farm
Scope : Site or Tenancy
Scope : SharePoint Site
Storage : List and Libraries
Storage : Any

68. Tools

69. SharePoint development across developer segments
End Users : who use the platform as an application platforms
Power Users: who create and administer ( & maybe brand) sites
Designers: who brand the site and build the user experience
Developer: who build and deploy apps
-Custom artifacts (web parts, lists, content types)
-Cloud-based apps/services
-Workflow
-…………
-Lightweight apps ( HTML, JS)
-Create Sites, lists, doc libraries etc
-Branding / themes
-…………
Design
Develop

70. SharePoint Designer 2013 SharePoint Designer 2013
Personalize pages, page layouts, web parts, web part pages, layouts and themes
Create and manage list and libraries
Design simple workflows or import workflows designed using Visio
Useful for creating rule-based, declarative workflow that can be imported in Visual Studio for deeper-level customization
Manage content types and site columns to model typed list of contents
Manage and register external data sources using BDC engine
Create pages with list data bound to external data sources
Manage users & groups
Manage files and assets of the target site
Evolved from FrontPage
Depending on your level of permission to a given site, some features may be hidden within the Designer IDE.eg: w/o admin privileges, we can’t see the Master Pages link in the Navigation pane
SPD uses the client-side SharePoint APIs and permissions to create artifacts in SharePoint on our behalf.

71. SharePoint Designer 2013
SharePoint Designer 2013 changes from previous version
No Design View - The Design View (the one that use to show the design at bottom with Split View) is no longer available in SharePoint Designer 2013.
Platform Type - SharePoint Designer 2013 you have the option of choosing the platform on which you wish to build a workflow in the workflow creation dialog. You can select SharePoint 2010 Workflow or SharePoint 2013 workflow.
Workflow Enhancements – Copy-paste workflow steps; Call external web-service from workflow; Loops in workflow; Dictionary type variables; workflow; New task actions;
stages

72. Napa
In SP2010, getting the dev environment set up took some time – locally install a number of software such as SP, SQL Server, Visual Studio and then configure them.
Napa enables us to quickly build and deploy solutions into SP using a rich browser-based approach.
We can also migrate the code we wrote in Napa to run and debug in Visual Studio as well.
Napa is really just another rich app the we can use to develop for SharePoint – can be downloaded from “Get tools to build apps” link in the SP developer site.
Lightweight apps can be built with ease of deployment.
Does not support rigorous and powerful set of capabilities such as those offered by Intellisense, ALM options, rich debugging etc.,

73. Napa Screenshots

74. Visual Studio 2012
Fully-features development IDE offers templates for us to build a variety of SharePoint apps and solutions
OOTB Project-level templates
SP2010 project / Sp2013 project – empty SP project that enables us to add one or more item-level templates to built a solution
Sp2010 Silverlight web part / SP2013 Silverlight web part – Rich media web part that uses Silverlight as the rendering engine
SP2010 Visual web part / Sp 2013 Visual web part – provides designer capabilities to drag and drop ASP .Net UI Controls and add code-behind
Import SP2010 Solution Package / Import SP 2013 Solution Package – enables to import and redistribute packaged solutions to the farm
Import reusable SP 2010 workflow / SP2013 workflows – enables us to import and then redistribute and deploy existing workflow solutions to the farm
OOTB item-level templates
List
Module
Remote Event Receiver
Client Web Part (Host Web)
Content Type
UI Custom Action (Host Web)
Workflow
Task Pane (App)
Empty Element
Content App
Site Column

75. Visual Studio 2012 – Server Explorer
Server Explorer manages the following :-
Sites & Subsites
Content Types
Features
List Templates
List and document libraries
Workflows

76. Evolution of customizations in SharePoint

77. Thank You