2. Welcome to SharePoint Saturday—The Conference Thank you for being a part of the first SharePoint Saturday conference Please turn off all electronic devices or set them to vibrate. If you must take a phone call, please do so in the hall so as not to disturb others. Open wireless access is available at SSID: SPSTC2011 Feel free to “tweet and blog” during the session Thanks to our Diamond and Platinum Sponsors:
5. Greg Hurlman: Consultant @ LiquidHub SharePoint Architect Developer Father Hokie Gamer World Famous Jungle Cruise Skipper (ret.)
6. What is a Service Application? Shared Service Providers are no more Limited function Limited scope Configuration hassles
7. What is a Service Application? Service Applications are the answer Fully extensible True “cloud” services More straightforward config
8. What is a Service Application? Service Applications are the answer Fully extensible True “cloud” services More straightforward config Custom Service Apps get a lot for free
9. Why a SharePoint Service? Custom Service Apps get a lot for free Settings Store Load balancing Easy use of SharePoint backup/upgrade/restore Provisioning infrastructure Service Discovery Administration UI SharePoint interaction totally optional (but silly not to)
10. When use a Custom Service? Yes Sharing data across SharePoint boundaries Long-running processes Encapsulating unique business logic Easy scalability No Site/Site Collection specific functionality Data/Features specific to a site template
11. Service Apps – How do they work? Made of many parts Database(s) Service itself Service Application Service Endpoint Service App Proxy Browser Client App SP Web Front End Web Parts, Events, etc. Service Application Proxy SP App Server Service Endpoints (*.svc, *.asmx) Consumed in many ways Web parts Event Listeners Workflows Application Pages Other Services Etc. Service Assemblies SQL Server Config DB Content DB(s) Custom DB
12.
13. What you’ll need Visual Studio 2010 Including the SharePoint Tools SharePoint Foundation Server Time
SPServiceEvery SPService object has an Instances property that holds all the instances of the service that are running on various servers in the farm. No more than one instance of each service runs on any one server, but some services have multiple instances, each one running on a different server. Each instance is represented by an object of a class derived from SPServiceInstance.SPServiceInstanceSPServiceInstance represents an instance of a service on a server in the farm. A service instance is independent from, and identical in functionality, to all other server instances of the same type. As long as one service instance of a given service remains online, the service is fully functional. Service instances may be in the ’started’ or ’stopped’ state. A service instance provides the host process for service applications.SPServiceApplicationA service application is hosted by a service instance. Service applications are generally created by administrators. They provide the service interface, containing the administrator settings. Service applications may own user data.SPServiceProxyA SPServiceProxy is simply the parent of the SPServiceApplicationProxy. It is the equivalent of a SPService on the server side, which is the parent of a SPServiceApplication. You can also think of these parent objects as class factories for the child objects, if that makes more sense to you.SPServiceApplicationProxyService application proxies provide the public (front-end) interface to a service application. They allow client code to consume remote service applications. Service applications may not be installed locally and therefore cannot be called directly.