Microsoft Office Tutorials and References
In Depth Information
Business Connectivity Service (or Business Data Connectivity Service in some circles) is new to
this version of SharePoint and very, very useful. It is manageable from this category of settings.
Service applications themselves are new to this version of SharePoint but otherwise are familiar
to those administrators who have worked with the SharePoint Server products. There are some
differences. Some things have been renamed, and some have been simplified. To start, these
service applications are all under the IIS Web Site named Web Services (an improvement over the
old shared service providers and their limitations in the SharePoint Server product).
Service applications often have corresponding applications listed in IIS under the Web
Services Web Site. They can have their own application pools, but because application pools
each use quite a bit of RAM, it’s considered a good idea to have as many of them use the same
application pool as possible (I am not really sold on that idea, but it has merit).
The Manage Service Applications page lists the service applications that are now available
in SharePoint Foundation (Figure 11.22): Application Discovery And Load Balancer Service
Application, Business Data Connectivity Service (if you have an instance enabled, which I do),
Security Token Service Application, and the Usage and Health data collection service (the only one
without a surfaced application in IIS). The two service applications, Business Data Connectivity
and Usage and Health (and their proxy connections), that can be configured in any way are in
blue; the others are listed in gray text. (If you enable and configure Subscription Settings service,
it can also show up on this page and in IIS. See Chapter 16 for more about that service.)
Application Discovery And Load Balancer Service Application Assists in sharing service
applications between trusts, keeps track of the service topology of the farm, and more. This is
also called the Topology service because it is uses the Topology application under SharePoint
Web Services in IIS.
Business Data Connectivity Service Allows SharePoint to access external data and expose
it within the web applications that associate with the service. This service must be
configured in order to allow external lists and lookups. When configured, it gets its own
application listed under the SharePoint Web Services Web Site in IIS. You can configure more
than one instance of this service application. See Chapter 16, “Advanced Installation and
Configuration,” for details about using Business Data Connectivity to surface external data.
Security Token Service The service application that makes claims-based
authentication possible and allows SharePoint to support security tokens. It uses the
SecurityTokenServiceApplication under SharePoint Web Services in IIS.
Usage and Health Data Collection Service Has its own database to store data but doesn’t
have its own application (and therefore, application pool) in IIS. It is used to collect usage and
health information for the entire farm.
Although you configured both the Usage and Health data collection service and Business
Data Connectivity in Chapter 3 (see that chapter for more details), I’ll quickly go over what each
button does when working with service applications. There are few service applications that can
be managed for SharePoint Foundation; this is an infrastructure feature more populated in the
Server version of this product.
Service applications often have additional connection, or proxy , settings. They can have more
than one connection configured. In this case, all the service applications listed have their own
proxies, except for the Security Token Service application.
Search JabSto ::

Custom Search