Session 2 Integrating SharePoint 2010 and Windows Azure


Published on

In this session we cover various ways of integrating SharePoint 2010 with Windows Azure and look at benefits and limitations of the different options. From simple to complex integration patterns, session will include SQL Azure and SharePoint integration with External Lists and Visual Web Parts, Azure hosted WCF Services integration with SharePoint using Silverlight and jQuery, and using SharePoint Event Handlers and workflows with Azure.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Windows Azure represents the core compute and management capabilities. For example, itprovides the core service management capabilities; developer tools, a portal through whichyou can configure your applications data, and services; and different types of storage (table,BLOB [binary large object], and queue) that offer non-relational data storage capabilities. Italso provides the Windows Azure Marketplace DataMarket as an offering that provides theability to integrate directly with subscription-based data that can be consumed programmaticallyor via the Marketplace browser user interface.SQL Azure represents the relational data storage for the cloud. You might think of SQL Azureas the SQL Server for the cloud; you can migrate or build relational databases that providerich and queryable data sources for your cloud-based or hybrid applications.Finally, Windows Azure AppFabric provides a set of middleware services and a way for youto build, connect, and manage services directly through the AppFabric service bus. This givesyou more flexibility and control over your cloud-hosted applications and also allows you totake advantage of core security features within the service bus.
  • Session 2 Integrating SharePoint 2010 and Windows Azure

    1. 1. SharePoint and Azure IntegrationIn this session we will cover various ways of integrating SharePoint 2010 with Windows Azure and look atbenefits and limitations of the different options.Contact Us About Me:201 Mission Street Amit ChachraSan Francisco, CA Principal Consultant,(415) 962-4600 Magenic
    2. 2. Agenda» Introductions» SharePoint Online with Sandbox Solutions » Overview » Advantages » Limitations » Workarounds and Addressing Limitations» Windows Azure » Introduction to the platform » Why integrate SharePoint 2010 and Windows Azure » Integration Approaches » Points of Integration
    3. 3. SharePoint OnlineSharePoint Online is a cloud-based service,hosted by Microsoft, for businesses of all sizes.Instead of installing and deploying MicrosoftSharePoint Server 2010 on premises, anybusiness can now simply subscribe to SharePointOnline to provide their employees with anenterprise-grade solution for creating sites toshare documents and information withcolleagues and customers.
    4. 4. SharePoint Online customization capability patternsCustomization Capability Tools and PatternCreate and deploy no-code workflows Use SharePoint Designer to create and deploy no-code workflows.Customize content types Use SharePoint Designer to customize content types.Brand master pages and create page layouts Use SharePoint Designer to brand master pages.Create and deploy site templates Use SharePoint Designer to create and deploy site templates.Consolidate, filter, roll up, and render data Use the Data View Web Part to create mash-ups, filtered views, rollups, and general renderings of SharePoint data or data consumed from web services or RSS feeds.Create browser-based forms Use Microsoft InfoPath 2010 to design browser-based forms for lists and workflows.Access and manipulate data from HTTP Use the SharePoint web services to access and manipulate data from HTTPrequests requests without writing code for that manipulation. Workflows also support new events that enable complex business processes to be chained together in a modular, manageable way.Create and deploy custom code-based Use Visual Studio 2010 to create code-based sandboxed solutions that can besolutions deployed to SharePoint Online environments.
    5. 5. Sandbox SolutionsEnables developers to deploy solutionswithout IT actionEnables IT to maintain health ofSharePoint serversIsolates custom code from running inSharePoint processQuicker time-to-market solutions for siteowners 5
    6. 6. Sandbox Solutions contd…» A sandboxed solution looks and behaves like a farm solution, but a sandboxed solution’s assembly must be marked to allow partially trusted callers.» Remember that a sandboxed solution can be deployed as a full-trust solution and gain the expanded capabilities that come with running in full trust because nothing in the .wsp solution file specifies it as a sandboxed solution or a farm solution. This is determined by how the solution is deployed.» Sandboxed solutions have access to a large subset of functionality in the Microsoft.SharePoint namespace. Essentially all the classes below SPSite are available.» In general, the sandbox process prevents you from accessing data outside the site collection where the solution has been deployed. 6
    7. 7. Sandbox Solutions - Advantages» Work directly with the customer (site collection owner)» Predictable limitations defined by SharePoint [SharePoint Online]» Speed to market – no need to involve administrator in deployment» Errors won’t affect the hosting SharePoint site 7
    8. 8. Sandbox Solutions - Limitations» Can only access subset of SharePoint 2010 server API» Blocked from making remote calls » Web service requests » ATOM feed requests » Custom database calls» Blocked from connecting to on-premise LOB systems» Limited to working in current site collection only» Blocked from accessing the Page object» Subject to resource monitoring & automatic throttling 8
    9. 9. Addressing Sandbox limitations Sandbox Solutions • Resource libraries that register specific actions can Utilize • Deployed as farm trust solution “Full-Trust” • Sandboxed solutions can call these deployed actions Proxies Move Business • Client-side Web Part – JavaScript / jQuery / etc Logic off Server • Silverlight Web Part 9
    10. 10. Processing model - Sandboxed solution calls a full-trust proxy 10
    11. 11. DemoFull trust proxy operation from a Sandboxed solution in SharePoint
    12. 12. Azure is an operating system in the cloud that enables reach, reusability and scale
    13. 13. Windows Azure Platform
    14. 14. Addressing SharePoint challenges with Windows Azure Break out of • Mitigate constraints imposed by sandbox the Sandbox • Achieve things not possible in thewith Windows sandbox in Windows Azure Azure Windows • Move business logic to Windows AzureAzure can solve • Host long-running processes a different • Access On-Prem systems via Service Bus • Advanced authentication via ACS problem 14
    15. 15. Why integrate Azure and SharePoint?» Scalable endpoint cloud-based data and services with SharePoint solutions» Migrate to hybrid or cloud-based custom services» Cost optimization» Integrate cloud with core features of SharePoint » E.g. Workflow, collaboration, search, document management, Silverlight, etc.» Extend Azure applications into Office» Parity across SharePoint & Office 365
    16. 16. Points of IntegrationAzure Integration HowSharePoint Client Object Model Interact with Windows Azure data in a list.Business Connectivity Services (BCS) Model data from Windows Azure or build external list to SQL Azure.Silverlight Create UI against Windows Azure services or data.Sandboxed Solutions/SharePoint Silverlight application leveraging Windows Azure deployed to site collection.OnlineOffice Custom Client Consume data directly from Windows Azure or BCS list exposing data.Standard/Visual 
Web Parts Leverage services and data from Windows Azure.Open XML Manage Windows Azure data in a document.REST Use REST to interact with Windows Azure data to integrate with SharePoint.Office Server Services Combine with Open XML to auto-gen docs (such as PDFs) on a server.Workflow/
Event Receivers State or events that tie into Windows Azure services, workflows or data.LINQ Use for querying Windows Azure data objects.Search Federate search to include Windows Azure data.
    17. 17. Integrating SharePoint 2010 & Windows Azure» Consume Windows Azure-based solution in SharePoint » Content Editor Web Part » Sandboxed Web Part » Business Connectivity Services / External Content Type » Search» Enable Windows Azure-based solution to interact with SharePoint » SharePoint Client Object Model (CSOM) » REST / OData feeds » SharePoint’s authentication configuration considerations » Classic Mode » Claims Based Authentication (ex: SharePoint Online)
    18. 18. SharePoint 2010 and Azure Integration scenarios Simple Moderate Complex • SharePoint hosted IFRAME • Client side solutions (CEWP) • Programmatic BCS with JavaScript & jQuery • Consuming custom Azure- • BCS with SharePoint hosted services Designer 2010 • Securing custom Azure- hosted services with certificates • Azure Access Control Services • Pluggable workflow services • Azure calling SharePoint via CSOM / REST / Web Services
    19. 19. ASP.NET and iFrame Content Editor Web Part SharePoint
    20. 20. and iFramePros ConsSimple& lightweight Styling & FormattingNo code No ‘deep’ integrationNo deployment to SP No Distribution through SP artifact
    21. 21. DemoCreate a Simple Azure Web Role and access it from within SharePoint usingiFrame
    22. 22. Azure Blob Storage
    23. 23. Azure Blob Storage and SharePoint
    24. 24. DemoAzure Blob Storage and SharePoint Integration
    25. 25. Consume Azure hosted service/data with Silverlight Web Part Web Part Silverlight BCS
    26. 26. DemoConsume a WCF service that is deployed to Windows Azure in a SharePointWeb Part
    27. 27. External Content Types - BCS
    28. 28. DemoExposing SQL Azure data using SharePoint External Content Types inRich Office Client
    29. 29. Azure DataMarket Data with SharePoint Excel Services
    30. 30. DemoIntegrating Azure DataMarket Data with SharePoint using ExcelServices
    31. 31. Windows Azure AppFabric • Use the Windows Azure AppFabric service bus to connect services deployed to Windows Azure (or the cloud in general) so that they can access and interact with SharePoint. • Interacting with SharePoint can mean reading and writing list data, updating site information, or creating new sites or content types in SharePoint (or literally anything you can do with the SharePoint APIs).
    32. 32. High Level Architecture – AppFabric Service Bus to access SharePoint
    33. 33. Summary» Sandbox Solutions » Overview » Challenges » Addressing Limitations» Building Apps with SharePoint Solutions» Addressing SharePoint Challenges with Windows Azure» Integrating SharePoint & Windows Azure
    34. 34. ReferencesFor Download » Download SharePoint VM » » Download Azure Developer Center » » Download SharePoint and Windows Azure Development Kit » » Windows Azure Marketplace DataMarket Whitepaper » Reference » Check out Steve Fox’s blog for code and walkthroughs » » Channel 9 SharePoint Developer Training Kit » » Channel 9 Azure Developer Training Kit »
    35. 35. Questions and Answers?Thank you