Your SlideShare is downloading. ×

SharePoint Fest Denver - SharePoint 2010 Integration and Interoperability: What You Need To Know

845

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
845
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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. 
  • 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
  • Transcript

    • 1. SharePoint 2010Integration and Interoperability:What you Need to Know
      Presented 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 Challenges
      SharePoint’s Important Interoperability
      What is the BCS?
      • External Content Types
      • 5. External Columns
      • 6. External Lists
      • 7. Extensibilityand Tooling
      4. Demonstration
      5. Limitations of BCS
      Bonus!
    • 8. Business Data Challenges
    • 9. Business Data in an Enterprise
      IT
      High Integration Costs (Custom)
      High Overhead (Maintenance, Security)
      Quality
      Financial
      Customers
      Operations
      Suppliers
      Quality
      Financial
      Customers
      Operations
      Suppliers
      Redundant Data and Processes!
      Users
      High Training Costs
      High Dissatisfaction
    • 10. Challengeswith Business Data
      Direct Impact
      Indirect Impact


    • 11. The Outcome
      There 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.
    • 13. SharePoint’s Important Interoperability
    • 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 Interoperability
      UI Platform
      Identity Platform
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 17. Is it a UI Platform?
      UI Platform
      Identity Platform
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 18. Why would we use SharePoint as a User Interface Platform?
    • 19. Consistent User Experience Across Browsers
      Well.. Almost.
    • 20. 1. By adhering to published interface standards.
      It’s a UI Platform
      HTML Standards
      UI Platform
      Identity Platform
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 21. A UI Platform Bonus?
      Bonus!
      HTML Standards
      UI Platform
      Identity Platform
      Works in Office
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 22. Leverage Office and SharePoint Interface Familiarity
    • 23. Is it an Identity Platform?
      HTML Standards
      UI Platform
      Identity Platform
      Works in Office
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 24. Why would we use SharePoint as an Identity Platform?
    • 25. Because Claims is Awesome
      Connect with 3rd Party Authentication Providers
      Connecting with a Non Windows Integrated Authentication driven web site.
      Delegation with Back-End Systems
      Showing data from another server on a SharePoint web page.
    • 26. 1. By adhering to published interface standards.
      Claims UsesConsistent Standards
      • WS-Federation 1.1
      Provides the architecture for a clean separation between trust mechanisms, security tokens formats, and the protocols for obtaining tokens.
      • WS-Trust 1.4
      Provides a method for assessing, requesting and receiving security tokens.
      • SAML Token 1.1
      XML 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 Platform
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 28. Is it aSearch Platform?
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Data Access Platform
      Storage
      External
      Data
    • 29. Why would we use SharePoint as a Search Platform?
    • 30. Query a 3rd Party Search Engine Using SharePoint UI
      Federate Queries to Multiple Search Systems…
    • 31. Index Content from a Range of Content Repositories
      What does all of these?
      _ _ _
      B C S
      B
      Indexes Databases, Web Services or Custom Repositories
      Provides Consistent Access to External Content
      C
      Has SharePoint Designer and Visual Studio Plug-ins
      S
    • 32. A Search Platform Bonus!
      Bonus!
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Open Search
      Data Access Platform
      Storage
      External
      Data
    • 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 2008
      Clients: Windows 7, IE, FireFox, Chrome, SharePoint …
      Providers: Amazon, Flickr, Wikipedia, SharePoint…
    • 37. It is a Search Platform
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Open Search
      Data Access Platform
      Storage
      External
      Data
    • 38. Is it a Data Access Platform?
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Open Search
      Data Access Platform
      Storage
      External
      Data
    • 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 2
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Open Search
      CMIS
      Data Access Platform
      REST
      Storage
      External
      Data
    • 42. Content Management Interoperability Services
      • CMIS 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 analyst
      A 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 REST
      Access 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 Interoperability
      HTML Standards
      UI Platform
      Identity Platform
      Claims
      Works in Office
      Search Platform
      Open Search
      CMIS
      Data Access Platform
      OData
      REST
      Some might even say it has storage interoperability or that OData is a standard…
      Storage
      External
      Data
      But the coolest part of interoperability?
      RBS
      BCS
    • 54. The Outcome
      SharePoint 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 Client
      BCS in Office Client
      Identity Federation
      service
      BCS in SharePoint
      BCS Meta
      Data Store
      BDC
      Client Data
      Cache
      BDC
      ASCustom
      Connector
      DB
      Connector
      WCF /WS
      Connector
      .NET Assembly
      Connector
      Client to Backend Direct Connection
      External data
      Persistence Store
      Data Cubes
      Custom .NET assembly
      SAP
      ORACLE
      Siebel
      SQL
    • 59. Or this simplified one…
    • 60. External Content Types
      Describes:
      • Structure of the external system (Fields, Methods, Connection)
      • 61. How this data behaves within SharePoint and Office
      Added to the BCS Service Through:
      • SharePoint Designer
      • 62. Visual Studio 2010
      • 63. Via an Import into the Business Data Connectivity Service as part of a model
      Manage and Re-Use from a Central Location
    • 64. External Lists
      The 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 Navigation
      Sort, Filter, Group
      Programmatic Access via SPList OM
      Profile Page for Each Item
      Form
      Auto-generated OOB
      Upsize to InfoPath
      Can be Taken “Offline”
    • 65. Offline Lists
      External Lists also be leveraged as Offline “Lists”
      They can be Downloaded to a SharePoint Workspace as Lists or Word Document Libraries with External Data Columns
      Or Connected to Outlook as Contacts, Tasks, Calendars and Posts
    • 66. Office Applications and Search
      External Content Types can also be leveraged in…
      Or Leveraged to allow for External Data Searching or Filtering
      Many other Office Applications (or Custom Applications)
      w/ Code
    • 67. Bonus! Integration Webparts
      Bonus!
      Integration Webparts
      Web Parts
      External Data List 
      External Data Item
      External Data Item Builder
      External Data Related List
      External Data Connectivity Filter
      Chart 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 Capability
      Claims Aware
      Connect via ADO/SQL, WCF/WS, .Net Assembly and Custom Connectors
      Batch and Bulk Operation Support
      BDC 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.
      Custom
      • Custom 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)
      Customize
      • InfoPath Forms
      • 75. Workflow
      • 76. Web Part Pages
      • 77. Outlook Taskpane and Ribbon
      Out-of-box
      • Surface data in External Lists
      • 78. Connect those lists to Outlook, SPW
      • 79. External Data Columns
      Intermediate
      Simple
      Advanced
      NO CODE
      “NO CODE”
      CODE
      SharePoint Designer
      SharePoint SDK
      Visual
      Studio
      Developer
      Power User
      Advanced Developer
    • 80. SharePoint Designer Process
      Discover your Data Source
      Map Operations to Data Source
      • Create, read, update, delete, lookup
      Connect to SharePoint and/or Office
    • Visual Studio Process
      • Upsize 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
    • 92. Suggested Life Cycle
    • 93. BCS Support Matrix
      N/A
      x
      x
      In code
      In code
      In code
      In code
      In code
    • 94. SharePoint Designer and Visual Studio
      Author External Content Types and Profile Pages
      • External Content Type Designer
      Connect to existing WCF/Web Services, Sql Server or .Net Assemblies
      Connect to virtually any data source through custom .Net code
      Data Connectivity
      Integrate External Data in WF
      • Workflow Designer
      Generate and Author External Lists and InfoPath Forms
      • Lists and Forms Designer
      SharePoint and Office
      Office Add-in Projects
      • Extend Office apps through BCS-aware code add-ins and reusable components
    • SharePoint Designer and Visual Studio
    • 95. The Outcome
      The 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!
    • 98.
    • 99. Demo!
    • 100. Inventory Example
    • 101. Inventory Example
    • 102. Inventory Example
    • 103. Permissions
      x
      x
      x
      x
    • 104. The Outcome
      You 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’.
    • 106. What are BCSLimitations?
    • 107. General BCS Limitations
      BLOB
      • No 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 Limitations
      • Workflows 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
      • 126. No attachments.
      External Lists
    • 127. Bonus!
      Bonus! External Column Limitations
      • You 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 types
    • Some Data Types Not Supported
      • No 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 Outcome
      You 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 Challenges
      SharePoint’s Important Interoperability
      What is the BCS?
      External Content Types
      External Columns
      External Lists
      Extensibility and Tooling
      Limitations of BCS
      The Challenges Aren’t All Technology Challenges
      Interface, Identity, Search and Data Access Platform
      A Set of Powerful Connection Capabilities
      Structured Types of External Content
      Leveraging External Content with Internal Content
      Interact Like SharePoint Lists
      Extensibility/Tool Range from UI to SPD to VS 2010
      Good 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
      • 138. LinkedIn: www.linkedin.com/in/rharbridge
      • 139. Email me at: richard@rharbridge.com
      • 140. My company: www.Allin.com
      • 141. Assessments: www.SharePointDiagnostics.com

    ×