Module 1

Module 1

Microsoft Microsoft Official SharePoint 2013 Course SharePoint 2013 Solution Highlights SharePoint Practice 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., History of SharePoint Versions SPS 2001 SPS 2003 MOSS 2007 SPS 2010 SPS 2013 STS (WSS v1) ASP 32 bit WSSv2 MOSS 2003 .NET 2.0 CMS 2002 32 bit WSSv3

MOSS 2007 .NET 3.0 (Used WF) VS 2005/2008 32 bit and 64 bit SP Foundation 2010 SP Server 2010 .NET 3.5 VS 2010 64 bit only SP Foundation 2013 SP Server 2013 .NET 4.5 VS 2012 64 bit only

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 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 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 SharePoint 2013 Wheel (Capabilities) Sites : Different types of sites available for use and features within the sites. Communities: Content: Core enterprise content management features Search: Insights: Communities and Social features such as blogs and Wikis Search driven features

Business Intelligence features such as KPI Composites: Ability to integrate external applications using BCS SharePoint 2010 Wheel (Capabilities) SharePoint Vision Customers Internet Presence Partners Enterprise Portal Employees HR, Finance, etc. XML Web Services Team Collaboration Business Applications Personal

(SAP, data warehouse, custom . . .) 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 Flavors of SharePoint 2013 SharePoint 2013 On-Premise Foundation On Cloud (No hassles of installation or deployment ) Enterprise 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, 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 SharePoint 2013 Technology Stack

Requires all-x64 bit environment Microsoft SharePoint Server 2013 Microsoft SharePoint Server 2013 Microsoft SharePoint Foundation 2013 Microsoft SharePoint Foundation 2013 .NET Framework and ASP.NET 4.5 .NET Framework and ASP.NET 4.5 Internet Information Services 7.5 Internet Information Services 7.5 SQL Server 2008 R2 / 2012 SQL Server 2008 R2 / 2012 Windows Server 2008 (x64 only) Windows Server 2008 (x64 only) Windows Server 2012(x64 only) Windows Server 2012(x64 only) Server Roles & Elements in a SharePoint Farm Front End Web Server (SharePoint 2013 + 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. SharePoint Farm Web Application Site Collection Site Application Server (SharePoint 2013 Installed ) Application servers host services such as indexing, Search, or Office Excel calculation services. Database Servers (SQL Server 2008 R2 / 2012) The database server hosts the content and configuration databases used by Office

SharePoint Server 2013. List/Document library Content Item SharePoint 2013 Architecture Logical Architecture Directory AD DS Authentication Claim based Authentication Default Users ADFS Load Balancer Request Management SharePoint 2013 Farm Application Pool 9 Application Pool 1 Central Administration Work

mgmt Service s Excel Services Published Intranet KM Portal Claims to DistributeDocument Conversion Windows d s Token Cache WFE 1 WFE 2 Content DB: 200 GB Word Services

App 1 App 2 App 3 Collaboration Portal Team Sites PowerPoint Access Services App Mgmt. Service Application Pool 5 User profile Content DB: 200 GB Application Pool 4 Managed Metadata Secure Store Services

Crawl DB Search Application Pool 8 Static Service S2S High Trust Web Application Application Pool 11 Machine Translation Web Application My Site Application Pool 6 Application Pool 7 Application Pool 8 BCS

ASP.NET Application (Provider Hosted FARM Solution) Application Pool 10 InfoPath Form Services Visio Graphic Services Line of Business Applications WFE 3 Application Pool 3 Application Pool 2 External Systems DBServer

Crawl DB And Other 2 SQLSharePoint Clustered/ DBs Mirrored DB servers Content Logs: 100 GB Temp DB: 100 GB Lync Server 2013 (Meetings, Audio, Video etc.) Content DB: 200 GB Workflow Manager (SharePoint 2013 Workflow Platform) Application Pool 12 Web App Search Center Office Web Application Server

Logical Architecture Logical Architecture Server Farms Service Applications Application Pools Content Database Zone Web Applications Site Collections Sites

Lists & Libraries Logical Architecture Physical Architecture Physical Architecture Farm Model Single Server Small Farm 1 x WEB/APP + SQL RAM (Per Server) 24 GB 16 GB WEB/APP 16 GB SQL CPU (Per Server) 4 Cores Medium Farm 2 WEB + 1-2 APP +

SQL 16 GB WEB 16 GB APP 32 GB SQL 4-8 Cores Large Farm 2-3 WEB + 2-3 APP + SQL 16 GB WEB 16 GB APP 32 GB SQL 4-8 Cores 4-8 Cores Hardware Requirements Web servers, application servers, and single server installations Installation Scenario

Deployment type and scale Single server with a Development or evaluation installation of built-in database or SharePoint Server 2013 or SharePoint single server that Foundation 2013 with the minimum uses SQL Server recommended services for development RAM 8 GB Processor Hard Disk space

64-bit, 4 80 GB for cores system drive 64-bit, 4 80 GB for cores system drive 64-bit, 4 80 GB for cores system drive 64-bit, 4

80 GB for cores system drive environments. Single server with a Development or evaluation installation of built-in database or SharePoint Server 2013 or SharePoint single server that Foundation 2013 running Visual Studio 2012 uses SQL Server and the minimum recommended services for 10 GB

development environments Single server with a Development or evaluation installation of built-in database or SharePoint Server 2013 running all available single server that services. 24 GB uses SQL Server Web server or Pilot, user acceptance test, or production application server deployment of SharePoint Server 2013 or in a three-tier farm

SharePoint Foundation 2013 12 GB Hardware Requirements Database Servers Component Processor Minimum requirement 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

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 (KB2671763 SharePoint 2013 Edition SharePoint Server 2013 Standard/Enterprise Edition Topology Supported Topologies Limited Deployments

Topology - Small Multi Purpose Four Server Farm Topology Medium Farm Six Server Farm Topology - Medium Farm + Office Web Apps Six Server Farm Load Balancer Topology - Large Large Farm Web servers for all incoming requests Dedicated web server(s) for crawling and administration Query and index servers All other search components

All other services (use these servers for the Central Admin site) Content databases and config uration database Search databases All other SharePoint databases Servers for running sandboxed code Topology - Hybrid Hybrid Farm Load Balancer Topology Stretched Farm O n-Prem ise COLO 54/2 4

192.1 68.1.2 54/24 1 92.1 68.1.100/24 10.1 0.1.10 2/24 19 1 04/2 4 19 V IP A ddre ss 20/2 4 192.1 68.1.1 20/2 4 10.1 0.1.10 7/24

19 Always O n Availability Group 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 New in SharePoint 2013 Contd..

Distributed Cache Service: The Distributed Cache service provides caching features in SharePoint Server 2013. 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 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 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 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) 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 its 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

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 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) Browser Support Matrix Browser Supported Internet Explorer 11 X Internet Explorer 10 X Internet Explorer 9 X Internet Explorer 8 X Not supported Internet Explorer 7

X Internet Explorer 6 X Google Chrome (latest released version) X Mozilla Firefox (latest released version) X Apple Safari (latest released version) X Mobile device OS OS version Browser

Smartphone device Windows Phone Windows Phone 7.5 or later IE Mobile Supported iOS 5.0 or later versions. Video play experience requires iOS version 6.0 or later. Safari Android Supported Supported 4.0 or later versions. Video play experience requires Supported Supported Android version 4.1 or later. Slate or tablet device Not applicable 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 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 Workflow Manager in SharePoint 2013 Whereas in previous versions workflow execution was hosted in SharePoint itself, this has changed in SharePoint 2013. 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 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. Itll 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 theyre SharePoint, for Windows applications, or Web applications. Theres also the ability to reuse the same Solution Architecture Overview Multi Languages Presentation Layer:- Responsive web layouts- HTML5 CSS3 Secure Access Gateway Authentication Integrate Web Server Application Server Social Collaboration The New App Model for SharePoint and Office Mobility Multi Device, Multi Channel Considerable support for Open Standards

Workflows Design Manager Enterprise Content Management Extended Cloud Support Unified Search Experience Connectors METRO Style UI Integration SharePoint 2013 Portal Components Line of Business 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 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, its part of search Architecture Changes Service Applications Sites Translation Docume service nt Streams OOB SP Designer Access Services SQL Server Storage Visual Studio Enables App creation

for running business Workflows Multi-lingual SharePoin t Front End Application management service App Store Licenses Purchase s App URL Infrastructure Enabler for New SP Apps New Services

Existing/Changed Services MMS User profiles Unified Search Services BCS Visio Enhanced Excel Services Discontinued Services Enhanced Powerpoin t Services Office Web Apps Service

3rd Party Servi ces Portal Web Analytics New Service Applications in SP 2013 Service App 1. App Management Service App New (available in SharePoint Foundation 2013 and SharePoint Server 2013) 1. SharePoint Translation Service (available only in SharePoint Server 2013 Std & Ent)

1. 1. PowerPoint Conversion Service Application (with SharePoint Server 2013 Std & Ent only) Work management Service Application (available only in SharePoint Server 2013 Std & Ent)

Features / Changes 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 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 jobautomated) 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 filesthe standard used by translation vendors 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 applications provides functionality to aggregate tasks to central place so that users can view and track their work and to-dos Tasks cached to persons 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 Improved Service Applications in SP 2013 Service App Business Data Connectivity service (available in Foundation & Server Versions) User profile service Features / Changes 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 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; (available only in 2013- Std & Ent) Word automation service (available only in SharePoint Server 2013 Std & Ent) Access Services App Databases (available only in SharePoint Server Enterprise 2013) Visio Graphics Services (available only in SharePoint Server Enterprise 2013) Excel Service

(available only in SharePoint Server Enterprise 2013) 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. 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. 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

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. Enterprise Content Management in SharePoint 2013 Enterprise Content Management in SharePoint 2013 Web Content Management in SharePoint 2013 Search in SharePoint 2013 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 Search in SharePoint 2013 - Search (FAST Integrated) Search: 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. Social Enhancements in SharePoint 2013 Social Enhancements in SharePoint 2013.. Social in SharePoint 2013 - Communities 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 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 using @mentions and #hash tags. Activity posts are saved for as long as you decide to retain them (most organizations align this policy with email 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). Social Enhancements in SharePoint 2013.. Task Aggregation: Single, aggregated, view of all user tasks across SharePoint Sites, Project Sites and Exchange BI in SharePoint 2013 BI in SharePoint 2013 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 97-2003 presentation format (.ppt) to .pptx, .pdf, .xps, .jpg, and .png. 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 Mobile in SharePoint 2013 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 Customization packaging and deployment options Farm Full trust solutions Customizations to file system of servers

Classic model from 2007 Sandbox Declarative elements Partially trusted code service still included for limited server side support SP Apps New Apps model Deployed from corporate catalog or office market place Manage permission and licenses specifically Preferred

option 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 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 dlls Makes migration difficult Permission model is very rigid and difficult to customize

Permissions cannot be configured for the solution itself very easily Impersonation has its own issues Hard to manage No support for upgrades and easy distribution and installation Developers must know SharePoint API 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 Benefits: APIs for manual deployment No custom code on the SharePoint Server Easier to upgrade Works in hosted environments without limitations Reduces the time for building these applications Dont need to be familiar with SharePoint APIs and concepts Versatility Allows you to use frameworks, languages, platforms that are not supported by SharePoint

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 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. Apps - Continued SharePoint-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 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 dont 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 doesnt 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 SharePoint Solutions & apps Hosting : Cloud v/s SharePoint Cloud Hosted SharePoint Hosted Preferred hosting model for Good for smaller apps and almost all types of apps recourse storage Full power of the web, Limited : No server-side code infrastructure and technology

allowed Requires a separate hosting Hosted within your SharePoint environment to be set up farm Additional administration and Managed as part of your management effort involved SharePoint farm Scope : Site or Tenancy Scope : SharePoint Site Storage : List and Libraries Storage : Any

Tools 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 -Lightweight apps ( HTML, JS) -Custom artifacts (web parts, lists, content types) -Create Sites, lists, doc libraries etc -Cloud-based apps/services -Branding / themes -Workflow - - Design

Develop 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 w/o admin privileges, we cant see the Master Pages link in the Navigation pane SPD uses the client-side SharePoint APIs and permissions to create artifacts in 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 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 browserbased 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., Napa Screenshots 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 itemlevel 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 List workflow solutions to the farm Module OOTB item-level templates Remote Event Receiver Client Web Part (Host Web) Content Type UI Custom Action (Host Web) Workflow Task Pane (App) Visual Studio 2012 Server Explorer

Server Explorer manages the following : Sites & Subsites Content Types Features List Templates List and document libraries Workflows Evolution of customizations in SharePoint Thank You

Recently Viewed Presentations

  • Food Service Sanitation For Classroom Staff -

    Food Service Sanitation For Classroom Staff -

    Your center's Persons in Charge are responsible for knowing, following and coaching all staff in the health and sanitary practices outlined by the department of health. The Health Department will inspect your food service program on a regular basis to...
  • Laplace Transform - University of Notre Dame

    Laplace Transform - University of Notre Dame

    Laplace Transform Melissa Meagher Meagan Pitluck Nathan Cutler Matt Abernethy Thomas Noel Scott Drotar The French Newton Pierre-Simon Laplace Developed mathematics in astronomy, physics, and statistics Began work in calculus which led to the Laplace Transform Focused later on celestial...
  • Chapter 1 Section 1 Part II

    Chapter 1 Section 1 Part II

    Chapter 1 Section 1 Part II Standard 10.1 Review Founder of Democracy in Athens Cleisthenes (KLYS-Thuh neez) Council of 500 Citizens debate and make law The Persian Wars In 500 B.C. Athens was the wealthiest City-State Persia had a large...
  • Discovering the Next Generation of Library Search Paul

    Discovering the Next Generation of Library Search Paul

    Even worse, when librarians assist users, satisfaction levels drop. One explanation for this is the "eat spinach" syndrome; that is, librarians try to show students what is good for them by instilling best practice, rather than conniving at the discovery...
  • Physics 114  General Physics II Everyone Pick Up:

    Physics 114 General Physics II Everyone Pick Up:

    30 cm metric ruler * - bring these to class ... Read the material assigned on the Web, or in class each day, before class starts Take a webassign-based reading quiz online by 9:30 AM You only get one chance...
  • Part 1-Section 1 Lines -

    Part 1-Section 1 Lines -

    Part 1-Section 1 Lines Unit 1 Bases for Blueprint Reading and Sketching Introduction Technical information through spoken or written word Shape, construction, simple geometries Methods of drawings Picture or photography Computer or technical sketch More accurate and detailed information provided...
  • Field Trip Expectations - PC\|MAC

    Field Trip Expectations - PC\|MAC

    Electronics. You may bring devices onto the bus ONLY if you have reached your AR goal for the year. Ms. Appleyard will pull the final report May 31st at lunch, and your homeroom teacher will announce by the end of...
  • SESAR & NextGen: Goals, Current State, Initial Implementation

    SESAR & NextGen: Goals, Current State, Initial Implementation

    STAMS LT Free Route - Advanced FUA AOC/CFMU improved traj UDPP Paris -Italy axis Advanced FUA, Mobile Mil Area Flight planning support with CTOT to TTA, UDPP Dynamic DCB SWIM enabled NOP ATC/NM IOP B1-ACDM - Optimised Airport Operations through...