Sharepoint - An Introduction
•Download as PPTX, PDF•
1 like•280 views
SharePoint is a cloud-based service that provides tools for communication, collaboration, and productivity for businesses and users. It includes services such as SharePoint Online, OneDrive, Yammer, Exchange Online, and Lync Online. SharePoint uses a service-oriented architecture and supports three types of apps: provider hosted apps, SharePoint hosted apps, and auto-hosted apps in the cloud. Licensing for SharePoint depends on usage scenarios such as intranet, extranet, or internet. SharePoint centralizes administration and allows customization, collaboration, security, and ease of use.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Sharepoint - An Introduction
Similar to Sharepoint - An Introduction (20)
Recently uploaded
Recently uploaded (20)
Sharepoint - An Introduction
- 2. Contents
- 11. Licensing
- 12. Licensing Scenario A : Intranet
- 13. Licensing Scenario B : Extranet
- 14. Licensing Scenario C : Internet
- 15. End users can manage licenses for apps they purchase through the SharePoint Store themselves a Users will be able to see a list of every app they’ve purchased and manage the licenses for it Farm admins can decide whether to let users purchase apps
- 16. Communication, Collaboration & Productivity tools for businesses and users Enterprise-grade cloud services Comprehensive tools to do your best work
- 17. • SharePoint Online • OneDrive • Yammer • Rich client • Web client • Apps • Lync Online• Exchange Online • Archiving • Encryption Email Real-time Communication CollaborationOffice
- 18. Provider Hosted Apps SharePoint Hosted Apps Preferred hosting model for almost all types of apps Good for smaller apps & resource storage Full power of web – choose your infrastructure & technology SharePoint-based; no server-side code May require your own hosting Automatically hosted in SharePoint May require you own handling of multitenancy & permission management Inherent multitenancy & isolation
- 19. SharePoint The app is hosted in the cloud. Windows Azure and SQL Server Azure components are provisioned automatically when an app is installed. (Available for SharePoint Online only) Existing sites and services App web (optional) Existing sites and services App web The app and all resources are hosted in your organization’s SharePoint farm. relies on client side technologies. Your IT organization supports the app. The app and all resources are hosted by the provider in any environment suitable for the app. Existing sites and services App web (optional) Oauth + REST or client object models Oauth + REST or client object models
- 20. Service applications in SharePoint 2013
- 21. Accounts
- 22. Service Accounts
- 23. Service Application list : SP 2013
- 24. Workflows
- 25. Workflow Server
- 27. Authentication
- 28. Path based site collections http://portal.cybosol.com/sites/sharepointstuff http://portal.cybosol.com/teams/spprojects http://portal.cybosol.com/sites/projecttracker http://projecttracker.cybosol.com
- 29. Host Header
- 30. Creating webapps
- 34. Centralized Administration Customizable Collaboration Site Consolidation Security Ease of use
- 35. Thank You
Editor's Notes
- Record Principle & Rules
- Susan With your evaluation of SkyDrive Pro, this becomes a natural extension of your Portal where you can share, store and collaborate on files. This approach lowers storage costs while still providing you with a seamless way to collaborate.
- -> Cache service: based on appfabric. Not supported from Azure yet. Activated on SP server level. (no technical detail available yet) -> Request management: Optimize WFE usage with optimal redirection of requests. Configured on Web app level with routing rules and health index.
- Here’s an example of what we’ll call a small farm. It is not a dedicated search farm so you can see we have other application servers to run all the other SharePoint service applications. For search specifically we’ve created separate servers for the index and query components, and another set for all the other search components. You’ll notice that we have added a replica for the index partition so we have high availability, and we’re keeping the query role with the index role for maximum query performance. You’ll also notice that all of the search components are highly available because they’ve also been created across host servers. So in this case all of the components are running on virtualized servers, but those virtual images are split across two hosts so if one host goes down, we don’t lose all of any one of the search service components. ********************************** From http://officecpub/Teams/itpro/Documents/O15%20Models/sp-2013-enterprise-search-model-.vsd From Olaf’s email: Note that the 4x VM need, is really a mapping of the need for 16 CPU cores for sufficient processing horsepower. On Win7 hosted VMs, that transfers to 4x VMs. Using physical servers or Win8 hosted VMs, there is no practical max CPU core per machine limitation, thus you can get away with only 2x machines as in O14. So 2x dedicated _machines_ for search is still supported, you although need to split those out into 4x VMs if running with Win7 has the host OS for the VMs. Topology diagrams are here: http://office/15/performance/IEG/Shared%20Documents/Productivity%20Search%20topologies%20v2.vsd
- In this case we’re bumping up the size of our corpus to 40 million items. We now have a dedicated search services farm, but in this diagram allow for the fact that if you wanted to have one big farm you could still do that – you would just add additional servers for the other service applications and add the service application databases to the SQL Servers. We’ve also increased the number of components. We now have four index partitions, with each partition having a replica for high availability. We still have two query processing components because that’s an adequate starting point unless we find we have enough load to require more. We’ve also bumped up the number of content processing components we have, to four. We’re only using two crawlers because relatively speaking that’s a lighter weight process retrieving the content, than actually processing it. ************************************** From http://officecpub/Teams/itpro/Documents/O15%20Models/sp-2013-enterprise-search-model-.vsd
- Here’s our large example, which is 100 million items. Now we’re clearly in a dedicated search services farm. You can see that we now have 10 index partitions, and each one has a replica for high availability. We’ve also increased the number of query processing components up to four to handle the increased load one might expect from that many items. On the content processing side we’re still just using two crawlers but we’re up to six content processing components, and we’re also up to six analytics components. Remember analytics activity is based on search activity, as well as usage activity and how many items have been crawled, so as our corpus size increases so will the demand on analytics. Again though, how many crawlers or any OTHER component you are going to need is going to be completely dependent upon how big your corpus is, how frequently it changes, what your freshness requirements are for indexed content, how much query load you have, etc. **************************** From http://officecpub/Teams/itpro/Documents/O15%20Models/sp-2013-enterprise-search-model-.vsd
- From OneNote with Eray
- Previous slide was about the SharePoint hosted apps, what’s the difference to provider hosted?
- Apps for SharePoint can be self-hosted by a developer, auto-provisioned by Azure, hosted by SharePoint, or a combination of these. All can leverage SharePoint components. Custom code can only be run in developer self-hosted or Azure auto-provisioned hosting options. The app is hosted in the cloud. Windows Azure and SQL Server Azure components are provisioned automatically when an app is installed. (Available for SharePoint Online Service only.)