With SharePoint Portal Server 2003, Microsoft introduced the Shared Services Infrastructure, which was essentially a set of services that can be configured at one time and can be shared across various web apps in the farm.
In MOSS 2007, Microsoft improvised on this with the concept of Shared Service Providers, which provided greater flexibility in deployment and configuration. For example, we could create more than one SSP in a farm and configure them differently and every web app could be associated with exactly one SSP. This helped in some ways, like the scenario where 2 web apps in the same farm needed to have different configurations for search.
The search results from one portal could be differentiated from another, if they were associated with separate SSPs in the farm that have different databases and processes.
In SharePoint 2010, this was replaced by "Service Applications" which had major architectural changes from SSPs of MOSS 2007 resulting in truly flexible deployment and granular delegation of control. Service isolation was a result of having separate content databases and configuration. This was seen as a major improvement over SSPs as they brought in more:
- Scalability (by being able to configure SAs on separate servers and control the server which provides the SA),
- Redundancy (by being able to be configured as load balanced across many servers in the farm),
- Independence (by running on different processes, each service application is independent of the other),
- Portability (by means of SA proxies)
And thus greater hardware utilization. Web applications established service connections to talk to these Service applications. The following are the list of Service Applications that were included in the SharePoint Server 2010:
- Access Services
- Application Registry
- Business Data Connectivity
- Excel
- Lotus Notes Connector
- Managed Metadata
- PerformancePoint
- Search
- Secure Store
- State
- Usage and Health
- User Profile
- Visio Graphics
- Web Analytics
- Word Automation
Due to the success of the service applications in SharePoint 2010, the general architecture has been retained in SharePoint 2013, although many new functionalities (in terms of the number of service applications and features in existing service applications) have been introduced and a few service applications reformed. The following table lists these changes.
| Service App |
Features / Changes |
|
1. App Management Service App - (available in SharePoint Foundation 2013 and SharePoint Server 2013) |
An app for SharePoint is a custom built application that provides a specific functionality to SharePoint end users. Apps for SharePoint can be purchased from the SharePoint Store which is hosted by Microsoft. Developers who develop SharePoint apps submit their apps to Microsoft which are published in the SharePoint store and are available for site owners or end users who can download and install an app to their SharePoint site. This Service app:
|
|
2. SharePoint Translation Service- (available only in SharePoint Server 2013 Std & Ent) |
|
|
3. Business Data Connectivity service (available in Foundation & Server Versions) |
|
|
4. User profile service (available only in SharePoint Server 2013- Std & Ent) |
Other features remain the same as in SharePoint 2010 |
|
5. Word automation service (available only in SharePoint Server 2013 - Std & Ent) |
|
|
6. Access Services App Databases (available only in SharePoint Server Enterprise 2013) |
Access Services 2013 doesn't expose an API that we can use to develop Access apps in Visual Studio. 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. Since this service app is now actually an App, it is isolated from the other stuff on our SharePoint Web Apps etc. For E.g., to bring data from this into a web part on our page, is not done directly, but has to be done through BCS.
|
|
7. Visio Graphics Services (available only in SharePoint Server Enterprise 2013) |
|
|
8. Work management Service Application - (available only in SharePoint Server 2013 - Std & Ent) |
|
|
9. Performance Point Service (available only in SharePoint Server Enterprise 2013) |
|
|
10. Application Discovery and Load Balancer Service Application (available in Foundation & Server Versions) |
Additionally, a SharePoint 2010 farm can consume services from a SharePoint 2013 Server farm. A web application can use both local and remote Service Applications from another farm. |
|
11. Excel Service (available only in SharePoint Server Enterprise 2013) |
Has been used since previous versions for Web-based interactive reporting and sharing and as a platform for building business applications
One deprecated feature from SharePoint 2010 to SharePoint 2013 is that we can't edit workbooks in the browser that have external data connections in SharePoint 2013 |
|
12. PowerPoint Conversion Service Application - |
|
|
13. Office Web Apps Service App |
This is no longer a Service Application. It has been made a separate product |
|
14. Web analytics service App |
Web Analytics is no longer a service application - analyses and reporting process are incorporated into the search service application |
|
15. Managed Metadata Service (with SharePoint Server 2013 - Std & Ent only) |
|
|
16. Lotus Notes Connector Service (with SharePoint Server 2013 - Std & Ent only) |
|
|
17. Search service app (with SharePoint Server 2013 - Std & Ent only) |
|
|
18. Secure store service app (with SharePoint Server 2013 - Std & Ent only) |
|
|
19. State service app (with SharePoint Server 2013 - Std & Ent only) |
|
|
20. Usage and Health Data collection service app (available in Foundation & Server Versions) |
|

Sandeep VemulaPosted Jul 1, 2014, 5:48 AM
very nice information