SharePoint Fest Denver - SharePoint 2010 Integration and Interoperability: What You Need To Know
Download as PPTX, PDF1 like886 views
SharePoint 2010 provides strong interoperability capabilities through its business connectivity services (BCS) which allow external data to be accessed and used within SharePoint. The BCS uses external content types to describe external data structures and metadata and make the data accessible through external lists, web parts, Office applications and search. It supports various external data sources through connectors that can retrieve and write data without custom code, improving integration with external systems.
SharePoint Fest Denver - SharePoint 2010 Integration and Interoperability: What You Need To Know
- 1. SharePoint 2010Integration and Interoperability:What you Need to KnowPresented By: Richard Harbridge@rharbridge
- 2. Who am I?I
- 3. Our Goal Today…From Here To Here
- 4. What we will be talking about…Business Data ChallengesSharePoint’s Important InteroperabilityWhat is the BCS?External Content Types
- 7. Extensibilityand Tooling4. Demonstration5. Limitations of BCSBonus!
- 9. Business Data in an EnterpriseITHigh Integration Costs (Custom)High Overhead (Maintenance, Security)QualityFinancialCustomersOperationsSuppliersQualityFinancialCustomersOperationsSuppliersRedundant Data and Processes!UsersHigh Training CostsHigh Dissatisfaction
- 10. Challengeswith Business DataDirect ImpactIndirect Impact
- 11. The OutcomeThere are challenges that disparate and disconnected business data systems cause.
- 12. What to watch out for…No system, product or application can completely solve business data challenges.
- 14. What the heck is Interoperability?(IHN-tuhr-AHP-uhr-uh-BIHL-ih-tee)“Interoperability is the ability of a system.. to work with other systems.. without special effort on the part of the customer.”How?
- 15. How do we achieve Interoperability?1. By adhering to published interface standards. Does SharePoint do this?SPOILER ALERT!2. By making use of a "broker" of services that can convert one system’s interface into another system’s interface "on the fly".What about this one?
- 16. SharePoint InteroperabilityUI PlatformIdentity PlatformSearch PlatformData Access PlatformStorageExternalData
- 17. Is it a UI Platform?UI PlatformIdentity PlatformSearch PlatformData Access PlatformStorageExternalData
- 18. Why would we use SharePoint as a User Interface Platform?
- 19. Consistent User Experience Across BrowsersWell.. Almost.
- 20. 1. By adhering to published interface standards. It’s a UI PlatformHTML StandardsUI PlatformIdentity PlatformSearch PlatformData Access PlatformStorageExternalData
- 21. A UI Platform Bonus?Bonus!HTML StandardsUI PlatformIdentity PlatformWorks in OfficeSearch PlatformData Access PlatformStorageExternalData
- 22. Leverage Office and SharePoint Interface Familiarity
- 23. Is it an Identity Platform?HTML StandardsUI PlatformIdentity PlatformWorks in OfficeSearch PlatformData Access PlatformStorageExternalData
- 24. Why would we use SharePoint as an Identity Platform?
- 25. Because Claims is AwesomeConnect with 3rd Party Authentication ProvidersConnecting with a Non Windows Integrated Authentication driven web site.Delegation with Back-End SystemsShowing data from another server on a SharePoint web page.
- 26. 1. By adhering to published interface standards. Claims UsesConsistent StandardsWS-Federation 1.1Provides the architecture for a clean separation between trust mechanisms, security tokens formats, and the protocols for obtaining tokens.WS-Trust 1.4Provides a method for assessing, requesting and receiving security tokens.SAML Token 1.1XML vocabulary used to represent claims in an interoperable way.* WS-Security… (various aspects) *Doesn’t actually support SAML Protocol (SAMLP)
- 27. It’s an Identity PlatformHTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformData Access PlatformStorageExternalData
- 28. Is it aSearch Platform?HTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformData Access PlatformStorageExternalData
- 29. Why would we use SharePoint as a Search Platform?
- 30. Query a 3rd Party Search Engine Using SharePoint UIFederate Queries to Multiple Search Systems…
- 31. Index Content from a Range of Content RepositoriesWhat does all of these?_ _ _B C SBIndexes Databases, Web Services or Custom RepositoriesProvides Consistent Access to External ContentCHas SharePoint Designer and Visual Studio Plug-insS
- 32. A Search Platform Bonus!Bonus!HTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformOpen SearchData Access PlatformStorageExternalData
- 33. 1. By adhering to published interface standards. Have you heard of OpenSearch?Standard (Creative Commons) for syndication and aggregation of search results
- 34. Syntax for executing queries
- 35. Results returned in RSS/ATOM + extensions
- 36. Supported by Microsoft Search Server 2008Clients: Windows 7, IE, FireFox, Chrome, SharePoint …Providers: Amazon, Flickr, Wikipedia, SharePoint…
- 37. It is a Search PlatformHTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformOpen SearchData Access PlatformStorageExternalData
- 38. Is it a Data Access Platform?HTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformOpen SearchData Access PlatformStorageExternalData
- 39. SharePoint Does a Great Job of Accessing SharePoint Content!
- 40. What about External Systems and Content?_ _ _B C S
- 41. A Data Access Platform Bonus!Bonus!x 2HTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformOpen SearchCMISData Access PlatformRESTStorageExternalData
- 42. Content Management Interoperability ServicesCMIS specification provides a Web services interface that:
- 43. Is designed to work over existing repositories enabling customers to build and leverage applications against multiple repositories—unlocking content they already have
- 44. Decouples Web services and content from the content management repository, enabling customers to manage content independently
- 45. Provides common Web services and Web 2.0 interfaces to dramatically simplify application development
- 46. Is development platform and language agnostic
- 47. Supports composite application development and mash-up by the business or IT analystA platform that allows you to build against multiple technologies without knowing anything about how all the API’s work. (If you know CMIS.)Microsoft has been implementing this from both a client and provider perspective.Not available “in the box”. Available via SharePoint Admin Toolkit
- 48. And then there’s RESTAccess to SharePoint Lists and Document Libraries…RESTful interface over HTTP
- 49. Uses the ADO.NET Data Services interface conventions
- 50. Feature rich: retrieve, update, browse data using just URLs and XML/JSON
- 51. Low barrier of entry. If you have an HTTP stack you can use it.Visual Studio Integration…Entirely built on top of the open RESTful interface
- 52. No client is required
- 53. Visual Studio creates proxies, visualizes schemas, provides LINQ support etc.2. By making use of a "broker" of services that can convert one system’s interface into another system’s interface "on the fly".SharePoint has InteroperabilityHTML StandardsUI PlatformIdentity PlatformClaimsWorks in OfficeSearch PlatformOpen SearchCMISData Access PlatformODataRESTSome might even say it has storage interoperability or that OData is a standard…StorageExternalData But the coolest part of interoperability?RBSBCS
- 54. The OutcomeSharePoint is a growing Interoperable UI, Identity, Search, and Data Access Platform.
- 55. What to watch out for…Remember this?“Interoperability is the ability of a system to work with other systems without special effort on the part of the customer.”without special effort
- 56. What is the BCS?
- 57. BCS External Data Benefits?External Data
- 58. You could look at this diagram…SharePoint ClientBCS in Office ClientIdentity FederationserviceBCS in SharePointBCS MetaData StoreBDCClient DataCacheBDCASCustomConnectorDBConnector WCF /WSConnector.NET AssemblyConnector Client to Backend Direct ConnectionExternal dataPersistence StoreData CubesCustom .NET assemblySAPORACLESiebelSQL
- 59. Or this simplified one…
- 60. External Content TypesDescribes:Structure of the external system (Fields, Methods, Connection)
- 61. How this data behaves within SharePoint and OfficeAdded to the BCS Service Through:SharePoint Designer
- 63. Via an Import into the Business Data Connectivity Service as part of a modelManage and Re-Use from a Central Location
- 64. External ListsThe external content type is leveraged in a variety of ways…Such as for Exposing External Data as an External SharePoint List Full CRUD capability Familiar UI and NavigationSort, Filter, GroupProgrammatic Access via SPList OMProfile Page for Each ItemFormAuto-generated OOBUpsize to InfoPathCan be Taken “Offline”
- 65. Offline ListsExternal Lists also be leveraged as Offline “Lists”They can be Downloaded to a SharePoint Workspace as Lists or Word Document Libraries with External Data ColumnsOr Connected to Outlook as Contacts, Tasks, Calendars and Posts
- 66. Office Applications and SearchExternal Content Types can also be leveraged in…Or Leveraged to allow for External Data Searching or FilteringMany other Office Applications (or Custom Applications)w/ Code
- 67. Bonus! Integration WebpartsBonus!Integration WebpartsWeb PartsExternal Data List External Data ItemExternal Data Item BuilderExternal Data Related ListExternal Data Connectivity FilterChart Web Part (New)w/ Code
- 68. Didn’t those webparts work with the BDC?
- 69. So what’s different? (Besides the Chart Control?)Read/Write CapabilityClaims AwareConnect via ADO/SQL, WCF/WS, .Net Assembly and Custom ConnectorsBatch and Bulk Operation SupportBDC is still used for search indexing connectors in 2010 they added blob, incremental crawl and item level security.They added symmetrical server and client runtimes. Allowing them to connect from client or server directly to external data.SQL CE database is used to cache external data which allows for “cached mode” behavior on external data basically creating a rich client cache.
- 70. How do I actually build it out?
- 71. Where things fit.CustomCustom connectivity for data aggregation, transformation, security, etc.
- 72. Use Custom Code to Integrate Data into any Office Application
- 73. Business Logic In Forms
- 74. Create Reusable Components (UI parts, ECTs, Actions)CustomizeInfoPath Forms
- 75. Workflow
- 76. Web Part Pages
- 77. Outlook Taskpane and RibbonOut-of-boxSurface data in External Lists
- 78. Connect those lists to Outlook, SPW
- 79. External Data ColumnsIntermediateSimpleAdvancedNO CODE“NO CODE”CODESharePoint DesignerSharePoint SDKVisualStudioDeveloperPower UserAdvanced Developer
- 80. SharePoint Designer ProcessDiscover your Data SourceDatabase
- 81. Web services
- 82. .NET typeMap Operations to Data SourceCreate, read, update, delete, lookupConnect to SharePoint and/or Office External List
- 83. Contact
- 84. Task
- 85. Appointment
- 86. PostVisual Studio ProcessUpsize IT Solutions Created in SharePoint Designer
- 87. Create Connectivity Packs in Visual Studio to
- 88. Aggregate data across multiple back-end systems
- 89. Perform custom data transformations
- 90. Execute custom business logic/rules (trigger workflow)
- 91. Bring External Data into other Office clients with VSTO Add-Ins (Excel)w/ Code
- 93. BCS Support MatrixN/AxxIn codeIn codeIn codeIn codeIn code
- 94. SharePoint Designer and Visual StudioAuthor External Content Types and Profile PagesExternal Content Type DesignerConnect to existing WCF/Web Services, Sql Server or .Net AssembliesConnect to virtually any data source through custom .Net codeData ConnectivityIntegrate External Data in WFWorkflow DesignerGenerate and Author External Lists and InfoPath FormsLists and Forms DesignerSharePoint and OfficeOffice Add-in ProjectsExtend Office apps through BCS-aware code add-ins and reusable componentsSharePoint Designer and Visual Studio
- 95. The OutcomeThe BCS has a bunch of new capabilities bundled with some old enhanced BDC ones.
- 96. What to watch out for…Selecting the right tool is important. Practice makes perfect.
- 97. That’s a lot of information!
- 99. Demo!
- 100. Inventory Example
- 101. Inventory Example
- 102. Inventory Example
- 103. Permissionsxxxx
- 104. The OutcomeYou saw how the BCS can be leveraged in SharePoint Designer and in the SharePoint UI.
- 105. What to watch out for…Don’t assume the tools will significantly reduce the time it takes to ‘integrate’. It typically reduces time to ‘interface’.
- 107. General BCS LimitationsBLOBNo Write support for BLOB
- 108. You cannot write back to BLOB fields using BCS unless you write your own method.
- 109. You can access BLOB columns by defining a StreamAccessor method and presenting the external data via the BCS Data List web part by checking the Display stream fieldsproperty.External List LimitationsWorkflows cannot be associated with external lists
- 110. Workaround: You can use the external data columns and manipulate it that way.
- 111. NoRSS feed support for external lists
- 112. No REST based access for external lists
- 113. http://sharepoint/_vti_bin/ListData.svc does not support external lists
- 114. LINQ to SharePoint spmetal.exe does not support external lists
- 115. Cannot configurealerts for external lists
- 116. Cannot export external list items to Excel (using the Export to Excel feature), Create Visio Diagram, Open with Access or Open with Project
- 117. Versioningcannot be configured on external lists
- 118. Version History is not available on external lists
- 119. Datasheet view cannot be used in external lists
- 120. XSLT is Supported (So you can basically make your own.)External Lists
- 121. External List Limitations Continued…Ratings feature is not supported for external lists
- 122. Information policies cannot be configured on external lists
- 123. Item-Level permissions are not available for external lists
- 124. No item or field level validation (without InfoPath)
- 125. Lookups don’t work on any column but ID
- 127. Bonus!Bonus! External Column LimitationsYou cannot create a site column of type ‘External Data Column’
- 128. External data columns can be created only as list based columns and cannot be consumed in site level content typesSome Data Types Not SupportedNo support for structs that are not simple types. (Do not use non-primitive structs.)
- 129. No nested collections (array of arrays etc)
- 130. No support for multi dimension arrays
- 131. BDC only works with .Net 3.5 - No dynamic programming in .Net 4
- 132. No support for ICollection or IEnumerableinterfaces to represent collections in data structures (ICollection<T>, IEnumerable<T>, IList<T>…)http://msdn.microsoft.com/en-us/library/ff621599.aspx
- 133. The OutcomeYou now know more about the limitations of BCS and will make fewer assumptions.
- 134. What to watch out for…Some of the many limitations mentioned make sense. Think carefully before you build a ‘workaround’.
- 135. What we talked about…Business Data ChallengesSharePoint’s Important InteroperabilityWhat is the BCS?External Content TypesExternal ColumnsExternal ListsExtensibility and ToolingLimitations of BCSThe Challenges Aren’t All Technology ChallengesInterface, Identity, Search and Data Access PlatformA Set of Powerful Connection CapabilitiesStructured Types of External ContentLeveraging External Content with Internal ContentInteract Like SharePoint ListsExtensibility/Tool Range from UI to SPD to VS 2010Good Enough and Better than Most Options
- 136. Thank You – Fill Out Your Eval! Organizers, Sponsors andYoufor Making this Possible.Twitter: @rharbridge
- 137. Blog: www.rharbridge.com
- 139. Email me at: richard@rharbridge.com
Editor's Notes
- #2: My dedication to you before I begin. By the end of this you will have gained 3 things. It might be new knowledge, it might be a new method but you MUST gain 3 things by the end. If you don’t my first challenge to you is to stalk me, hunt me down and make sure you get 3 things from me. Because I owe you 3 things! This is meant to help you.
- #81: A lot of this can seem daunting and I know one of the hardest things is figuring out how to do some of the things I have shown today. If you are interested in further training or assistance please let me know. Based on the number of people who are interested and the areas of interest we can schedule further training sessions to help everyone better use the SharePoint portal.It's our commitment to you that we will continue to hear your feedback and identify the issues. I encourage you to give us feedback during the coming months, and we will continue to deliver more and more functionality, more and more guidance to help you be successful with your application of SharePoint.Thank You for Reading/Listening