Custom Applications - What, When, and Why
-
Upload
greg-hurlman -
Category
Technology
-
view
463 -
download
0
description
Transcript of Custom Applications - What, When, and Why
Hello!
Welcome to SharePoint Saturday—The Conference Welcome to SharePoint Saturday—The 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:
Thank you for being a part of the first SharePoint Saturday conference
Developing Custom Service Applications: When, Why, & How
Who are you?
Greg Hurlman:Consultant @ LiquidHubSharePoint ArchitectDeveloperFatherHokieGamerWorld Famous Jungle Cruise Skipper (ret.)
What is a Service Application?
• Shared Service Providers are no more– Limited function– Limited scope– Configuration hassles
What is a Service Application?
• Service Applications are the answer– Fully extensible– True “cloud” services–More straightforward config
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
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)
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
Service Apps – How do they work?
• Made of many parts– Database(s)– Service itself– Service Application– Service Endpoint– Service App Proxy
SQ
L S
erv
er
Config DB
Content DB(s)
Custom DB
SP A
pp
S
erv
erService Assemblies
Service Endpoints (*.svc, *.asmx)
SP W
eb
Front
End
Service Application Proxy
Web Parts, Events, etc.
BrowserClient App
• Consumed in many ways– Web parts– Event Listeners– Workflows– Application Pages– Other Services– Etc.
Anatomy of a Service App• SPIisWebService
– Really a definition
• SPIisWebServiceInstance– One instance/server
• SPIisWebServiceApplication– Provides the internal service interface– May own user data
• SPIisWebServiceProxy– Again, really a definition
• SPIisWebServiceApplicationProxy– Provides the front-end interface– Allows for client code consumption
ClassFactories
What you’ll need• Visual Studio 2010– Including the SharePoint Tools
• SharePoint Foundation Server• Time
Demo!
Questions?
Photo Credits• http://www.flickr.com/photos/photojonny/2268845904/• http://www.flickr.com/photos/magdalar/2950663799• http://www.flickr.com/photos/damaradeaella/2822846819/
Welcome to SharePoint Saturday—The Conference
Thanks to Our Other Sponsors!Thanks to our Sponsors
Thanks for coming!
• Don’t forget your evaluations
• Find me at:
http://about.me/greghurlman