It is about how SharePoint started and how it is useful to any organization.

1. SharePoint
2010
Sunday, June 23, 2013
Author:
Saurabh Parikh
Referenced by:
Jigar Acharya

2. Overview
• What is SharePoint?
• SharePoint is a central enterprise information portal, that can be configured to run Intranet, Extranet
and Internet sites. In brief, SharePoint is all about sharing data i.e. centralize data.
• What SharePoint Product and Technologies Composed of?
• Windows SharePoint Service 3.0 (WSS)
• Microsoft Office SharePoint Server 2007 (MOSS)
• What is difference between WSS and MOSS?
• Microsoft has divided SharePoint product in two parts i.e. WSS and MOSS.
• WSS is a platform on which MOSS is built. The WSS Part is licensed through windows 2003 server and
it does not cost.
• MOSS is a separate product by itself which need licensing and it has good amount of cost.
• WSS is good for small team and small projects while MOSS has extra functionalities i.e. value added
service.
• So the choice between WSS and MOSS will depend on budget of the project and the extra
functionality i.e. value added service provide by MOS
Sunday, June 23, 2013

3. What is SharePoint?
• Collaboration : Allow teams to work together effectively, collaborate on and publish
documents, maintain task lists, implement workflows, and share information through the use
of wikis and blogs.
• Features provided by SharePoint
• Content Management: Create and manage documents, records, and Web content.
• Portal: Create a personal My Site portal to share information with others and
personalize the user experience and content of an enterprise Web site based on the
user’s profile
• Search: Quickly and easily find people, expertise, and content in business applications.
• Business Intelligence: Allow information workers to easily access critical business
information, analyze and view data, and publish reports to make more informed
decisions.
• Business Processes: Create workflows and electronic forms to automate and
streamline your business processes.
Sunday, June 23, 2013

4. SharePoint Architecture
• This figure shows the relationship of WSS with IIS
and SQL Server.
Sunday, June 23, 2013
 SharePoint uses ASP.NET runtime to parse
any request but it add some more handlers
and modules which pass request to
SharePoint runtime and it passes through to
ASP.NET runtime

5. Share Point Version
• Microsoft has released several generations of SharePoint, but we only need to be concerned with SharePoint
2007, which has been around for roughly 3 years now, and SharePoint 2010, which was officially released in May
2010.
• SharePoint 2007 has mainly 6 functionalities while SharePoint 2010 has upgraded with many new and better
features.
Sunday, June 23, 2013

6. Earlier SharePoint versions…
2001
• SharePoint
Portal Server
2003
• Windows
SharePoint
Services 2.0
• Microsoft
SharePoint
Portal Server
2003
2007
• Windows
SharePoint
Services 3.0
• Microsoft
Office
SharePoint
Server 2007

7. Architecture
Sunday, June 23, 2013
SharePoint server 2007 SharePoint server 2010

8. Why SharePoint Version 2010?
This are major features which are in SharePoint 2010:
• Sites:
• User can have read/write capability in office integration.
• Web analysis can be done in enterprise management operation.
• User can edit to mobile and can view full-fidelity in mobile connectivity.
• Microsoft Silverlight can be used for user experience.
• Tagging, office web applications, audience targeting are also included in SP2010.
• Communities: There are lots of community features like,
• ask me about
• note board, organization browser
• social bookmarks
• my networks
• Wikis
Sunday, June 23, 2013

9. Why SharePoint Version 2010?
• Content: content is new in SharePoint 2010. It has features like,
• Compliance Everywhere
• Flexible Records Management
• Shared Content Types And Managed Metadata Service
• Content Organizer
• Rich Media Management
• Document Sets
• Word Automation Services
• Support For Accessibility Standards
• Composites:
• Business Connectivity Services
• Visio Services
• Access Services
• Sandboxed Solutions
Sunday, June 23, 2013

10. Why SharePoint Version 2010?
• Search:
• Refinement Panel And Sorting
• Search In Context
• Social Behavior Improves Relevance
• Thumbnails, Previews, And View In Browser
• Insights:
• Enhanced Navigation, Including Filtering And Sorting (Top/Bottom 10, Switchable
Measures)
• Publish more workbooks
• PowerShell scripting
• Richer fidelity with excel workbooks
• Additional Data Sources, Including External Lists And “PowerPivot” Workbooks
• Seamless Management Of Dashboard Content
• Improved Visualizations
• Chart Web Parts
Sunday, June 23, 2013

11. SharePoint 2013
• What is SharePoint 2013::
 A new version of Microsoft famous Collaboration portal called SharePoint. The version adds few
new exciting features such as Social Feed, SharePoint Apps and cross-site publishing.
New features in SharePoint 2013 are as follows::
Development Changes –
• In SharePoint 2013 Microsoft Introduced a new Cloud App Model for designing Apps for SharePoint. Apps for
SharePoint are self-contained pieces of functionality that extend the capabilities of a SharePoint website. You can use
HTML, CSS, JavaScript and protocols like the Open Data protocol (OData), and OAuth to communicate with SharePoint
using Apps.
• Tools – SharePoint 2013 has Introduced new Tools for App development. Visual Studio 2012 now lets you develop apps
for SharePoint and apps for Office. In addition a new web-based tools called “Napa” Office 365 Development Tools
were introduced for developing apps.
• No more Sandbox solutions. SharePoint 2013 sandboxed solutions are deprecated. So all we got is the New App model
and the Old SharePoint Farm solutions.
Sunday, June 23, 2013

12. SharePoint 2013
Social and Collaboration features – Microsoft in SharePoint 2013 Introduced new Social capabilities for better
collaboration in the company. New Features added are
• Interactive feed
• Community Site
• Follow people
• Follow Sites
Search - SharePoint 2013 includes several enhancements, custom content processing with the Content
Enrichment web service, and a new framework for presenting search result types. Some of the features added
are –
• Consolidated Search Results
• Rich Results Framework
• keyword query language (KQL) enhancements
Enterprise Content Management (ECM) -SharePoint 2013 added some of the best capabilities of an ECM
software. The newly added stuff is
• Design Manager
• Managed Navigation
• Cross-site Publishing
• EDiscovery
Sunday, June 23, 2013

13. SharePoint Products & Technologies
Sunday, June 23, 2013

14. Products of SP2010
• In the SharePoint 2007 product line, the “free” version is officially known as WSS 3.0, or Windows
SharePoint Services 3.0, which is rebranded in the 2010 product line as SharePoint Foundation
2010.
• This version (in both the 2007 and 2010 product lines) offers a core set of collaboration and
document management tools. Microsoft also provides a more feature-rich version that, in the
SharePoint 2007 product line, is titled SharePoint Server 2007; this is now called SharePoint
Server 2010 in the current version and, like the 2007 product, comes in Standard and Enterprise
editions.
• Requirements::
• SharePoint Server 2010 will be 64-bit only.
• SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows
Server 2008 R2.
• SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
• Run the Pre-UpgradeCheck.
Sunday, June 23, 2013

15. Site Templates:
• Team
• Blank
• Document Workspace
• Blog
• Group Work Site
• Basic Meeting Workspace
• Blank Meeting Workspace
• Decision Meeting Workspace
• Social Meeting Workspace
• Multipage Meeting Workspace
Site Collection Features:
• Custom Site Collection Help
• Open Documents in Client Applications by Default
• Report Server Integration Feature
• Three-state Workflow
Service Applications:
• User and Health
• Security Token Service (STS)
• Claims to Windows Token Service
• Application Discovery and Load Balancer Service
• Subscription Settings Service
• Sandboxed Code Service
• SharePoint Foundation Search Service
• Workflow Timer Service
• State Service
Site Features:
• Group Work Lists
• Report Server File Synch
• Team Collaboration Lists
• Wiki Page Home Page
Sunday, June 23, 2013

16. –Standard
Site Collection Features:
• SharePoint Server Standard Site Collection
Features
• SharePoint Server Publishing
Infrastructure
• Publishing approval Workflow
• Content Type Syndication Hub
• Disposition Approval Workflow
• Document ID Service
• Document Sets
• In Place Records Management
• Library and Folder Based Retention
• Reporting
• Search Server Web Parts
• Workflows
• SharePoint 2007 Workflows
Site Features:
• SharePoint Server Standard Site Features
• SharePoint Server
• Content Organizer
• E-mail integration with Content Organizer
• Hold and eDiscovery
• Metadata Navigation and Filtering
• Offline Synchronization for External Lists
Site Templates:
• Records Center
• Enterprise Search Center
• My Site Host
• Basic Search Center
• Publishing Portal
• Enterprise Wiki
Service Applications:
• Search Service
• Managed Metadata Service
• Secure Store Service
• Word Automation Service
• User Profile Service
• Web Analytics Service
Sunday, June 23, 2013

17. –Enterprise
Service Applications:
• Access Service
• Excel Service
• PerformancePoint Service
• Visio Graphics Service
• Lotus Notes Connector Service
• Application Registry Service
Site Templates:
• Business Intelligence Center
• FAST Search Center
• Visio Process Repository
Site Collection Features:
• SharePoint Server Enterprise Site
Collection Features
• Performance Point Service Site
Collection Features
Site Features:
• SharePoint Server Enterprise Site
Features
Sunday, June 23, 2013

18. Web Server
• When user want to host the application on a centralized location and
wanted to access from many locations, Web server is responsible for
handle all the requests that are coming from clients, process them and
provide the responses.
Sunday, June 23, 2013

19. How IIS works?
1. Whenever a request comes from Client to Server, it will hit HTTP.SYS First.
2. HTTP.SYS is Responsible for pass the request to particular Application pool.
But How HTTP.SYS comes to know where to send the request?
 Whenever user creates a new Application Pool, the ID of the Application Pool is being generated and it’s
registered with the HTTP.SYS. So whenever HTTP.SYS Received the request from any web application, it
checks for the Application Pool and based on the application pool it send the request.
3. Web Admin Services (WAS) takes the request from HTTP.SYS and pass it to the respective application
pool.
4. When Application pool receive the request, it simply pass the request to worker process.
5. The worker process looks up the URL of the request in order to load the correct ISAPI extension.
 ISAPI extensions are the IIS way to handle requests for different resources. Once ASP.NET is installed,
it installs its own ISAPI extension (aspnet_isapi.dll) and adds the mapping into IIS.
6. When Worker process loads the aspnet_isapi.dll, it start an HTTPRuntime, which is the entry point of an
application.
 HTTPRuntime is a class which calls the ProcessRequest method to start Processing.
7. When this methods called, a new instance of HTTPContext is been created. Which is accessible using
HTTPContext.Current Properties. This object still remains alive during life time of object request.
Using HttpContext.Current we can access some other objects like Request, Response, Session etc.
8. After that HttpRuntime load an HttpApplication object with the help of HttpApplicationFactory class..
Each and every request should pass through the corresponding HTTPModule to reach to HTTPHandler,
this list of module are configured by the HTTPApplication.
Sunday, June 23, 2013

20. Sunday, June 23, 2013
9. HTTPHandler contains a set of HttpModules that intercept the request on its way to the
HttpHandler. So it is called HTTPPipeline.
 HTTPModules are classes that have access to the incoming request. We can also create our own
HTTPModule if we need to handle anything during upcoming request and response.
10.HTTP Handlers are the endpoints in the HTTP pipeline. All request that are passing through the
HTTPModule should reached to HTTPHandler.
11.Then HTTP Handler generates the output for the requested resource. So, when we requesting
for any aspx web pages, it returns the corresponding HTML output.

21. Web Farm
• when there is huge amount of incoming traffic for any web sites, one
standalone server is not sufficient to process the request. User may
need to use multiple servers to host the application and divide the
traffic among them. This is called “Web Farm”.
• So when user is hosting his/her single web site on multiple web
servers over load balancer is called “Web Farm”.
Sunday, June 23, 2013

22. Web Farm
• In general web farm architecture, a single application is hosted on
multiple IIS Server and those are connected with the VIP (Virtual IP)
with Load Balancer. Load Balancer IPs are exposed to external world
to access. So whenever some request will come to server from clients,
it will first hit the Load Balancer, then based on the traffic on each
server, LB distributes the request to the corresponding web server.
These web servers may share the same DB server or may be they can
use a replicated server in the back end.
Sunday, June 23, 2013

23. Web Farm and Sandbox
Web farm
• Hosted in IIS worker process.
• It will affect the whole farm.
• In web farm, solutions are installed
and deployed.
• In this, user can create application
page.
Sandbox
• Hosted in the SharePoint user code
solution worker process.
• It will only affect the site collection
of the solution.
• In sandbox, solutions are uploaded
and activated.
• In this application pages can’t be
created because user don’t have
permission to physical folder.
Sunday, June 23, 2013
• The sandbox is designed to bring greater stability to a SharePoint farm by restricting
actions that could cause problems with performance, security, or other areas.
• This stability is achieved by limiting the functionality accessible to custom code
solutions through the use of code access security (CAS) policies and by restricting
access to portions of the object model.

24. SP Object Model - Server Architecture
Sunday, June 23, 2013

25. Object Model – Site Architecture
Sunday, June 23, 2013
More Details

26. REFERENCES
Sunday, June 23, 2013
 http://www.intranetjournal.com/sharepoint/
 http://www.fpweb.net/sharepoint-hosting/free-
sharepoint-tutorials.asp
 http://drewmace.blogspot.com/2008/01/top-10-reasons-
to-implement-sharepoint.html
 http://www.codeproject.com/Articles
 http://blog.eukhost.com/webhosting/difference-
between-windows-sharepoint-services-and-sharepoint-
servers

27. Sunday, June 23, 2013