Sharepoint as a service platform
-
date post
21-Oct-2014 -
Category
Technology
-
view
2.643 -
download
2
description
Transcript of Sharepoint as a service platform
Kashif Akram
Microsoft Community Speaker
Dev30
SHAREPOINT AS A SERVICE PLATFORM
What is Sharepoint
MICROSOFT SHAREPOINT 2010THE BUSINESS COLLABORATION PLATFORM FOR THE ENTERPRISE AND THE INTERNET
Deliver the Best Productivity Experience
Cut Costs with a Unified Infrastructure
Rapidly Respond to Business Needs
Communities
Search
Sites
Composites
ContentInsights
NEW DIMENSIONS OF SHAREPOINT
A Service Platform
A Application Development
Platform
WHAT IS A SERVICE PLATFORM
It provide facilities for application design, application development, testing, deployment and hosting as well as application services such as team collaboration, web service integration and marshaling, database integration, security, scalability, storage, persistence, state management, application versioning, application instrumentation
APPROACH
WHAT WE NORMALLY FORGET DURING TRADITIONAL APPROACH • Governance
• End user empowerment
• Security
• Hosting
• Consumption
• System Integrity across enterprise
SERVICES PLATFORM PROVIDES • SP can a number of benefits to an organization including software reuse, better alignment
with business processes and lower cost and agile development cycles. However, achieving these benefits requires building on top of a platform that provides a number of capabilities including:
• 1) Governance and Registry
• 2) Extension
• 3) Administration / Control
• 4) Security
• 5) Tooling
ASP.NET 2.0 (AJAX)
Windows 2003
IIS
NET Framework 3.0
WSS 3.0
Document Management
Security Content Types Windows Workflow
SQL Server
MOSS 2007 EnterpriseEnterprise
SearchUser
Profiles
LOB Integration
(BDC)
Excel Services
Enterprise Content
ManagementMy Sites Records
Management
SHAREPOINT 2007 (MOSS)
SO, WHAT WAS “BAD“ ABOUT SSP’S ?
SSP’s • Big improvement, but some limitations
All or nothing • Search / Profiles / Excel / BDC
Not extensible • No custom SSP
No granularity • Web application tied to specific SSPs
Sharing across farms • Tied to a single farm (shared-farm SSP’s possible but tricky)
ARCHITECTURE
1. Define the WCF endpoint2. Implement the business logic and package
(Maybe webservices, or windows services )3. Implement SAF 4. Create or reuse persistence store
ARCHITECTURAL VIEWService: Actual program (binaries)deployed to servers in farm
Service Application
Service Proxy Service Proxy
Web Part, Pages(Service
Consumer)
*.SVC’s, PowerShell Cmdlets
(Service Consumer)
Service Machine Instance: Actual instance of the running service binaries on a server
Service Application: Configuration of the servicein a farm
Service Application Proxy:Reference to the Service Application
Service Consumer: Bits that utilize the service’s logic
SERVICE APPLICATIONS (SP2010)
Flexibility • New services model much more flexible
A la carte • Just pick the one you need
Common Framework • Build custom using framework
Sharing • Single farm or shared across farms
Scalability • Entire farms can be dedicated to service hosting and computing
SERVICE APPLICATION FORMWORK • SAF is designed around an abstract model of service providers and consumers. This
abstract model provides the hooks that SharePoint uses to provide a unified management experience for a large variety of services
• Services that implement this model may be integrated with SharePoint features such as the Farm Configuration Wizard, the “Services on Server” and “Service Applications” management UX, and SharePoint backup/restore, to name a few.
• A middle-tier service is not part of a SharePoint web application or site, and is not directly accessed by end users. It is typically accessed from a Web Front End server (WFE) on behalf of an end-user request
• for example, the “Search Box” web part executing on a WFE invokes a middle-tier “Search Query” service application to retrieve raw search results, which are then rendered to HTML by the web part
Farm 3Farm 2Farm 1
http://www.dev30.comhttp://intranet
Search
User Profile
s
Search
Excel
UserProfile
s
ManagedMetadata
SERVICE APPLICATIONS
SERVICES APPLICATION OBJECT MODEL
5 configuration object types: SPService, SPServiceInstance, SPServiceApplication, SPServiceProxy, and SPServiceApplicationProxy.
SPSERVICE (SERVICE)• The SPService class represents a service that has been registered in a SharePoint
server farm.
SPSERVICEINSTANCE (SERVICE INSTANCE)• The SPServiceInstance class represents a service (SPService) that has been installed
(but not necessarily started) on a specific application server (SPServer) in a SharePoint server farm. An SPServiceInstance has a Status property that indicates whether or not the service instance has been started.
SPSERVICEAPPLICATION (SERVICE APPLICATION)• The SPServiceApplication class represents a logical service endpoint (to which a service
consumer connects).
• This endpoint may actually consist of many physical endpoints; that is, the service application may be hosted on many application servers for additional reliability and scalability. These physical endpoints are represented by online (started) SPServiceInstance objects.
SPSERVICEPROXY (SERVICE PROXY)• The SPServiceProxy class represents a service consumer (client) that has been
registered in a SharePoint server farm.
• A custom SPServiceProxy may be installed by a SharePoint solution or a custom MSI, and registered when a server farm administrator activates a SharePoint farm-scoped feature or executes a PowerShell script.
SPSERVICEAPPLICATIONPROXY (SERVICE APPLICATION PROXY)• The SPServiceApplicationProxy class represents a logical connection to a service
application.
SERVICE PLATFORM FEATURES
• Settings (config database)• Web service provisioning• Database provisioning• Service discovery• Integrated round-robin load balancer• Claims based authentication• Backup & restore
Core infrastructure
• Central Administration UI• Permissions• PowerShell
Management
SERVICES
TO BUILD A SERVICE APPLICATIONCreate a service application
Create a WCF service application endpoint
Write the service application installation code
Install and provision the service application
Create the service application proxy
Write the service application proxy installation code
Install and provision the service application proxy
Create the service application consumers
Install, deploy, and test the service application consumers
CREATE A SERVICES
DEMO
Download code
http://blogs.msdn.com/b/dtaylor/archive/2010/06/11/calculator-service-source-code.aspx
CREATE A SERVICE APPLICATION
• Demo
CREATE A SERVICE APPLICATION UI
• Demo
CREATE CLIENT PROXY
• Demo
• Thank you