Consultancy Soup

Some points I captured from Microsoft Training about server roles Web Front End servers Web Front End (WFE) servers form the connection point for clients that request content or services from SharePoint. Every request from a client is directed to a WFE server, and every response to a client is sent from a WFE server. This means that all client requests place some load on WFE servers. A WFE server is responsible for: • Processing incoming requests through IIS. • Requesting any data from service applications and databases that is required to service the request. • Processing the data returned by service applications and databases. • Compiling responses as ASP.NET pages and sending the responses to the requestor. In small farms, WFE servers often perform application roles in addition to the WFE role. WFE servers do not require large quantities of disk storage; instead, they rely heavily on processor power and memory for performance. Some service applications, e

Some points i captured from Microsoft training about  SharePoint Performance Factors Typically, the performance of a web platform such as SharePoint is quantified using four key measures: latency, throughput, data scale, and availability. Latency SharePoint 2013 latency can suffer in many different areas, including: • Network latency, also referred to as round trip time (RTT). • Available network bandwidth, which affects how long it takes to send back the whole of the response. • Uncompressed data transmission. • Custom code elements, such as Web Parts or features that are not well optimized. You can only determine the server processing and client rendering elements of latency through performance testing. However, you may have access to case studies that can provide a benchmark to assist in determining general requirements. Throughput Throughput is the number of requests that a server farm is able to process in a fixed period. To create a SharePoint fa

Here you are some links that are useful when building and deploying apps (provider hosted and auto hosted) http://spbreed.wordpress.com/2013/11/25/deploying-mvc5-based-provider-hosted-apps-for-on-premise-sharepoint-2013/ http://spcaca.blogspot.co.uk/2013/10/create-on-premise-high-trust-provider.html http://www.sharepointnutsandbolts.com/2013/07/deploying-sp2013-provider-hosted.html

Important tools/code when developing/administrating SharePoint Code Analysis: http://blogs.msdn.com/b/codeanalysis/ http://csslint.net/ http://www.jshint.com/ http://www.microsoft.com/en-us/download/details.aspx?id=38196 https://spdisposecheck2012.codeplex.com/ CAML Designer: used to create the CAML queries hat is used in SP data retrieval http://biwug-web.sharepoint.com/SitePages/Caml_designer.aspx http://karinebosch.wordpress.com/my-articles/caml-designer-for-SharePoint-2013/ Apps samples http://code.msdn.microsoft.com/sharepoint/SharePoint-2013-Use-event-8b5a551f http://code.msdn.microsoft.com/sharepoint/Remote-Authentication-in-b7b6f43c http://code.msdn.microsoft.com/sharepoint/Apps-for-SharePoint-sample-64c80184/view/SamplePack#content http://code.msdn.microsoft.com/sharepoint/SharePoint-2013-Sample-81b03d1e/view/SamplePack#content http://code.msdn.microsoft.com/sharepoint/Apps-for-SharePoint-sample-64c80184/view/SamplePack#content Clien

Developer Dashboard used to track issues/performance and calls which is an effective tool for developers to check their code to enable it using powershell $sp2010 = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings $sp2010.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::On $sp2010.RequiredPermissions = 'EmptyMask' $sp2010.TraceEnabled = $true $sp2010.Update() To Disable it: $sp2010 = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings $sp2010.DisplayLevel = [Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::Off $sp2010.Update()

Creates a session state database and turns on the session state service. $serviceApp = New-SPStateServiceApplication -Name "<StateServiceName>" New-SPStateServiceDatabase -Name "<StateServiceDatabase>" -ServiceApplication $serviceApp New-SPStateServiceApplicationProxy -Name "ApplicationProxy" -ServiceApplication $serviceApp -DefaultProxy

This is different than enabling state service application Enable-SPSessionStateService –DatabaseName “SessionStateDatabase” –DatabaseServer “localhost” –SessionTimeout 120