Microsoft Office Tutorials and References
In Depth Information
BAD SOLUTION, NO DINNER FOR YOU…
Solutions can be pointed to the User Code service and, using something called solution affinity , be made
to r un only on the ser vers that have this ser v ice star ted. Any sandboxed solution (which now includes
site templates) is allowed only so many “resource points” within which to run. If a solution exceeds its
allowed points, it’s turned off. The user using the solution may not know what’s going on or be able do
anything about it, but now you can sleep safely, knowing that at least it isn’t crashing the server.
A few services that SharePoint uses straddle the line between a SharePoint capability, service
application (which uses an application pool identity to function), and a simple service. They
include the following:
Business Data Connectivity Service (BDC) This Business Data Connectivity Service
application enables external connection types, such as non-SharePoint SQL databases,
which allows SharePoint to surface that non-SharePoint data in external lists. It uses the
Web Services web application in IIS and has its own application pool identity to function.
Although it isn’t a separate service running in the Services console or Task Manager, it has its
own database and an identity, which you can specify. This service is also known as Business
Connectivity Service (or BCS) in some documentation.
KEEPIN’ IT BRIEF
Most of these services, if you were to look at them in Central Administration, would start with the
words Microsoft SharePoint Foundation and then the actual unique task the service does, such as User
Code Service. I’ve taken the liberty of shortening these titles to avoid too much repetition.
Application Discovery and Load Balancer Service Application This service simply
supports load balancing and discovery of farm-scoped applications. It doesn’t really have its own
service account and has no configuration settings to speak of.
Subscription Settings Service This service, for the most part, is not surfaced for
configuration in Central Administration. A number of service applications normally used by
SharePoint Server 2010 have been moved to SharePoint Foundation, and this is one of them.
The Subscription Settings service applies to something called multi-tenancy . This kind
of SharePoint setup requires configuration via PowerShell; it cannot be done in Central
Administration. It basically uses a GUID to put site collections together in a “subscription.”
Very much the way SharePoint online works, it allows for a SharePoint implementation to be
configured in such a way that each department or client has their own SharePoint “deploy-
ment” with limited administrative surface. This service also allows the farm administrator
to create “feature packs” or group together features and then apply them to certain
subscriptions, giving those site collections only the features available in the pack. For more about
multi-tenancy, see Chapter 16.
Workflow Timer Service A subservice of the SharePoint Timer service that runs the farm,
this service simply sets the number of workflow events that are processed every timer
interval for the server.