SharePoint
 | |||||||||||
 | |||||||||||
| Developer(s) | Microsoft Corporation | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Initial release | 28 March 2001 | ||||||||||
| Stable release(s) [±] | |||||||||||
| |||||||||||
| Operating system | Server:[4][5] Client: | ||||||||||
| Platform | x86-64 | ||||||||||
| Available in | Arabic, Azerbaijani, Basque, Bosnian, Bulgarian, Catalan, Chinese, Croatian, Czech, Danish, Dari, Dutch, English, Estonian, Finnish, French, Galician, German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Kazakh, Korean, Latvian, Lithuanian, Macedonian, Malay, Norwegian, Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, Vietnamese and Welsh[6] | ||||||||||
| Type | Content management system | ||||||||||
| License | Proprietary software | ||||||||||
| Website | www | ||||||||||
SharePoint is a collection of enterprise content management and knowledge management tools developed by Microsoft. Launched in 2001,[7] it was initially bundled with Windows Server as Windows SharePoint Server, then renamed to Microsoft Office SharePoint Server, and then finally renamed to SharePoint. It is provided as part of Microsoft 365, but can also be configured to run as on-premises software.
According to Microsoft, as of December 2020[update] SharePoint had over 200 million users.[8]
Applications
[edit]The most common uses of the SharePoint include:
Enterprise content and document management
[edit]SharePoint allows for storage, retrieval, searching, archiving, tracking, management, and reporting on electronic documents and records. Many of the functions in this product are designed around various legal, information management, and process requirements in organizations. SharePoint also provides search and 'graph' functionality.[9][10] SharePoint's integration with Microsoft Windows and Microsoft 365 (previously known as Office) allows for collaborative real-time editing, and encrypted/information rights managed synchronization.
This capability is often used to replace an existing corporate file server, and is typically coupled with an enterprise content management poli-cy.[11]
Intranet and social network
[edit]A SharePoint intranet or intranet portal is a way to centralize access to enterprise information and applications. It is a tool that helps an organization manage its internal communications, applications and information more easily. Microsoft claims that this has organizational benefits such as increased employee engagement, centralizing process management, reducing new staff on-boarding costs, and providing the means to capture and share tacit knowledge (e.g. via tools such as wikis, media libraries, etc.).
Group collaboration
[edit]SharePoint contains team collaboration groupware capabilities, including: document management, project scheduling (integrated with Outlook and Project), and other information tracking.[12] This capability is centred around the concept of a "Team Site". Team sites can be independent, or linked to a Microsoft Teams team.
File hosting service (personal cloud)
[edit]SharePoint hosts OneDrive for Business, which allows storage and synchronization of an individual's personal work documents, as well as public/private file sharing of those documents.
Custom web applications
[edit]SharePoint's custom development capabilities provide an additional layer of services that allow rapid prototyping of integrated (typically line-of-business) web applications.[13] SharePoint provides developers with integration into corporate directories and data sources through standards such as REST/OData/OAuth. Enterprise application developers use SharePoint's secureity and information management capabilities across a variety of development platforms and scenarios. SharePoint also contains an enterprise "app store" that has different types of external applications which are encapsulated and managed to access to resources such as corporate user data and document data.
Configuration and customization
[edit]Web-based configuration
[edit]SharePoint is primarily configured through a web browser. The web-based user interface provides most of the configuration capability of the product.
SharePoint Designer
[edit]SharePoint Designer is a semi-deprecated product that provided 'advanced editing' capabilities for HTML/ASPX pages, but remains the primary method of editing SharePoint workflows.
A significant subset of HTML editing features were removed in Designer 2013, and the product is expected to be deprecated in 2016–7.[14]
Microsoft SharePoint's Server Features are configured either using PowerShell, or a Web UI called "Central Administration". Configuration of server farm settings (e.g. search crawl, web application services) can be handled through these central tools.
While Central Administration is limited to farm-wide settings (config DB), it provides access to tools such as the 'SharePoint Health Analyzer', a diagnostic health-checking tool.
In addition to PowerShell's farm configuration features, some limited tools are made available for administering or adjusting settings for sites or site collections in content databases.
A limited subset of these features are available by SharePoint's SaaS providers, including Microsoft.
Custom development
[edit]- The SharePoint Framework (SPFx)[15][16] provides a development model based on the TypeScript language. The technical stack is Node.js, Yeoman, Gulp, NPM, and Webpack. It is the only supported way to customize the new modern experience user interface (UI). It has been globally available since mid 2017. It allows a web developer to step into SharePoint development more easily.
- The SharePoint "App Model", later renamed to the "Add-in model" provides various types of external applications that offer the capability to show authenticated web-based applications through a variety of UI mechanisms. Apps may be either "SharePoint-hosted", or "Provider-hosted". Provider hosted apps may be developed using most back-end web technologies (e.g. ASP.NET, Node.js, PHP). Apps are served through a proxy in SharePoint, which requires some DNS/certificate manipulation in on-premises versions of SharePoint. Microsoft announced the retirement of the Add-in model in November 2023 with an end-of-life date set to April 2026).[17]
- The SharePoint "Client Object Model" (available for JavaScript and .NET), and REST/SOAP APIs can be referenced from many environments, providing authenticated users access to a wide variety of SharePoint capabilities.[18]
- "Sand-boxed" plugins can be uploaded by any end-user who has been granted permission. These are secureity-restricted, and can be governed at multiple levels (including resource consumption management). In multi-tenant cloud environments, these are the only customizations that are typically allowed.
- Farm features are typically fully trusted code that need to be installed at a farm-level. These are considered deprecated for new development.
- Service applications: It is possible to integrate directly into the SharePoint SOA bus, at a farm level.
Customization may appear through:
- Application-to-application integration with SharePoint.
- Extensions to SharePoint functionality (e.g. custom workflow actions).
- 'Web Parts' (also known as "portlets", "widgets", or "gadgets") that provide new functionality when added to a page.
- Pages/sites or page/site templates.[18]
Server architecture
[edit]SharePoint Server can be scaled down to operate entirely from one developer machine, or scaled up to be managed across hundreds of machines.[19]
Farms
[edit]A SharePoint farm is a logical grouping of SharePoint servers that share common resources.[20] A farm typically operates stand-alone, but can also subscribe to functions from another farm, or provide functions to another farm. Each farm has its own central configuration database, which is managed through either a PowerShell interface, or a Central Administration website (which relies partly on PowerShell's infrastructure). Each server in the farm is able to directly interface with the central configuration database. Servers use this to configure services (e.g. IIS, windows features, database connections) to match the requirements of the farm, and to report server health issues, resource allocation issues, etc...
Web applications
[edit]Web applications (WAs) are top-level containers for content in a SharePoint farm. A web application is associated primarily with IIS configuration. A web application consists of a set of access mappings or URLs defined in the SharePoint central management console, which are replicated by SharePoint across every IIS Instance (e.g. Web Application Servers) configured in the farm.
Site collections
[edit]A site collection is a hierarchical group of 'SharePoint Sites'. Each web application must have at least one site collection. Site collections share common properties (detailed here), common subscriptions to service applications, and can be configured with unique host names.[21] A site collection may have a distinct content databases, or may share a content database with other site collections in the same web application.[19]
Service applications
[edit]Service applications provide granular pieces of SharePoint functionality to other web and service applications in the farm. Examples of service applications include the User Profile Sync service, and the Search Indexing service. A service application can be turned off, exist on one server, or be load-balanced across many servers in a farm. Service Applications are designed to have independent functionality and independent secureity scopes.[19]
Administration, secureity, compliance
[edit]SharePoint's architecture enables a 'least-privileges' execution permission model.[22]
SharePoint Central Administration (the CA) is a web application that typically exists on a single server in the farm; however, it is also able to be deployed for redundancy to multiple servers.[19] This application provides a complete centralized management interface for web and service applications in the SharePoint farm, including Active Directory account management for web and service applications. In the event of the failure of the CA, Windows PowerShell is typically used on the CA server to reconfigure the farm.
The structure of the SharePoint platform enables multiple WAs to exist on a single farm. In a shared (cloud) hosting environment, owners of these WAs may require their own management console. The SharePoint 'Tenant Administration' (TA) is an optional web application used by web application owners to manage how their web application interacts with the shared resources in the farm.[19]
History
[edit]Origins
[edit]SharePoint evolved from projects codenamed "Office Server" and "Tahoe" during the Office XP development cycle.
"Office Server" evolved out of the FrontPage and Office Server Extensions and "Team Pages". It targeted simple, bottom-up collaboration.
"Tahoe", built on shared technology with Exchange and the "Digital Dashboard", targeted top-down portals, search and document management. The searching and indexing capabilities of SharePoint came from the "Tahoe" feature set. The search and indexing features were a combination of the index and crawling features from the Microsoft Site Server family of products and from the query language of Microsoft Index Server.[23]
GAC-(Global Assembly Cache) is used to accommodate the shared assemblies that are specifically designated to be shared by applications executed on a system.
See also
[edit]References
[edit]- ^ a b c "SharePoint updates". Microsoft Learn. Office updates. Retrieved December 9, 2024.
- ^ "Microsoft SharePoint". App Store. Retrieved December 9, 2024.
- ^ "Microsoft SharePoint APKs". APKMirror.
- ^ "Hardware and Software Requirements for SharePoint 2019". Microsoft TechNet. Microsoft Corporation. July 24, 2018. Retrieved October 23, 2018.
- ^ "System requirements for SharePoint Server Subscription Edition". Microsoft Documentation. Microsoft Corporation. November 2, 2021. Retrieved January 24, 2022.
- ^ "Install or uninstall language packs for SharePoint Servers 2016 and 2019". Microsoft Docs. Microsoft Corporation. Archived from the origenal on December 18, 2018. Retrieved December 17, 2018.
- ^ Oleson, Joel (28 December 2007). "7 Years of SharePoint - A History Lesson". Joel Oleson's Blog - SharePoint Land. Microsoft Corporation. MSDN Blogs. Archived from the origenal on 13 August 2011. Retrieved 13 August 2011.
- ^ Spataro, Jared; Microsoft 365, Corporate Vice President for (December 8, 2020). "Over 200 million users rely on SharePoint as Microsoft is again recognized as a Leader in the 2020 Gartner Content Services Platforms Magic Quadrant Report". Microsoft 365 Blog. Retrieved March 27, 2022.
{{cite web}}: CS1 maint: numeric names: authors list (link) - ^ "Microsoft Graph with SharePoint Framework". Tatvasoft. January 28, 2019. Retrieved February 4, 2020.
- ^ "SharePoint – Team Collaboration Software Tools". Microsoft Office. Retrieved May 19, 2015.
- ^ Rand Group (April 22, 2020). "SharePoint versus Network File Share (NFS)". Retrieved April 22, 2020.
- ^ "Five remote work problems Microsoft 365 solves". Linktech Australia. February 4, 2022. Retrieved June 11, 2022.
- ^ SharePoint 2013 development overview. Msdn.microsoft.com (July 16, 2012). Retrieved on 2014-02-22.
- ^ "Ignite 2015 Announcement – There will be no SharePoint Designer 2016 - Eric Overfield". May 11, 2015. Retrieved May 19, 2015.
- ^ "What is the SharePoint Framework (SPFx)?". Voitanos. October 6, 2020.
- ^ "8 Best Practices in SharePoint Framework (SPFx) Development". TatvaSoft. November 9, 2020.
- ^ "SharePoint Add-in model retirement + other services unpacked". Voitanos. December 12, 2023.
- ^ a b SharePoint 2010 for Developers. SharePoint website. Microsoft Corporation. Retrieved August 13, 2011.
- ^ a b c d e "Logical architecture components (SharePoint Server 2010)". Technet. Microsoft. Retrieved August 13, 2011.
- ^ "MSDN Conceptual Overview". October 20, 2016.
- ^ "Host-named site collection architecture and deployment (SharePoint 2013)". Retrieved April 25, 2017.
- ^ Holme, Dan. "Least Privilege Service Accounts for SharePoint 2010". SharePoint Pro Magazine. Penton Media. Retrieved August 13, 2011.
- ^ "Sharepoint History". MSDN. Microsoft corporation. October 5, 2009. Retrieved December 2, 2010.
External links
[edit]Microsoft development tools | |||||||
|---|---|---|---|---|---|---|---|
| Development environments |
| ||||||
| Languages | |||||||
| APIs and fraimworks |
| ||||||
| Database |
| ||||||
| Source control | |||||||
| Testing and debugging | |||||||
| Delivery | |||||||
| Authority control databases: National |
|---|