Consuming External Data with Business Connectivity Services in SharePoint 2010

2. Consuming External Data with Business Connectivity Services in SharePoint 2010 Name Title Company

3. Agenda • Business Connectivity Services (BCS) Primer • Creating BCS Applications • BCS Security • BCS And Search

4. Business Connectivity Services (BCS) Primer

5. Business Connectivity Services SharePoint Office Applications Design Tools BCS Client Dev Platform Business Intelligence Enterprise Content Management Collaboration Social Enterprise Search SharePointDesigner External Lists External Content Type Repository Visual Studio Business Data Connectivity LOB Web Service WCF DB Web 2.0

6. Data & Connectivity SharePoint Client BCS in Office Client BCS in SharePoint Identity Federation service BCS Meta Data Store Client Data Cache BDC BDC DB Connector WCF /WS Connector .NET Assembly Connector ASCustom Connector Client to Backend Direct Connection External data Persistence Store Custom .NET assembly Data Cubes SQL SAP ORACLE Siebel

7. External Content TypesThe building block Describes the schema and data access capabilities of an external data source and its behavior within Office and SharePoint *formerly known as BDC Entity Office Clients (Rich) BCS External Data Source (Web Service, DB, .Net object, LOB system, Web 2.0 service, etc.) External Content Type (ECT) BCS BCS-enabled solutions rely on ECTs to integrate external data into SharePoint and the Office client applications SharePoint (Thin)

8. BCS Server Features by SKU

9. BDC Runtime • Client & Server symmetrical model • Write back capable • Batch read operations • Navigate and create associations • Bulk APIs • Read blobs (streaming support) • Read and write back complex types (Dot notation) • Uniform experience across various systems types • Extensibility mechanisms • .NET Assembly Connector • Custom Connector • Secure Store Provider (custom)

10. External Content Type Modeling with SPD demo

11. Creating BCS Applications

12. Out-of-box Surface data in External Lists Connect those lists to Outlook, SPW External Data Columns Solution Types • Custom connectivity for data aggregation, transformation, security, etc. • Use custom code to integrate data into any Office app • Business logic in forms • Create reusable components (UI parts, ECTs, actions) • Customize • InfoPath forms • Workflow • Web Part Pages • Outlook taskpane and ribbon Simple Intermediate Advanced NO CODE* CODE SharePoint Designer SharePoint SDK Visual Studio Developer Power User Advanced Developer

13. Solution Creation Approaches • Client-Server Environment • Compose solutions (no code) that connect to existing WCF, Sql Server databases and .Net Objects • Implicitly author thin and rich client UX for External List and InfoPath Forms • Single machine Dev Environment • Create reusable ECTs that provide custom integration logic to virtually any data source using .Net code • Author thin and rich client UX as reusable components • Create Office Add-Ins in Visual Studio Import & Configure Produce WSP “Live” Connection Export, Import & Configure Developer Power User Visual Studio SharePoint Server (Shared, Dev/Prod) SharePoint Designer IT Admin Production Environment SharePoint Designer SDK

14. Exposing Your Data From SharePoint • External Data Columns • External Lists • Chart WebPart • Business Data WebParts • Business Data List/Related List • Business Data Item Builder • Business Data Item • BDC OM • SharePoint OM • Client Side OM (CSOM) No Code Solutions Custom Code

15. BDC Models in VS 2010 • BDC Model SharePoint Project Item (SPI) • Farm Feature with Feature Receiver ImportModelReceiver • BDC Model Designer • BDC Explorer • Minimal XML editing

16. Using BDC OM

17. Bulk API Example - Model

18. Bulk API Example - Code

19. Batching API Example - Model

20. Batching API Example - Code

21. SharePoint & Client Side OM • Expose ECT as External List • CSOM • Use List and ListItem • SharePoint OM • Use SPList, SPListItem for CRUD • Limitations • Type must be represented within Table • ID Field type must be Int32 • No Bulk or Batching API Support • SPListItem not strongly typed • No BLOB streaming support

22. Creating a .Net Connector in Visual Studio 2010 demo

23. BCS Security

24. BDC Authentication SharePoint Server Process Account Modes: PassThrough (Uses logged-on user) RevertToSelf (Uses process account) SSO Authentication (Credentials, etc. from Secure Store) Application CredentialsTicket Delegation Token Other BCS Runtime WebPart VL Logged-on user Secure Store Service Application Delegated Token SAML Token Credentials Claims Aware Service Web 2.0 Legacy LOB

25. Secure Store Service (SSS) • Used to avoid double-hop issue • Can be used for Impersonation • BDCAuthException throw when • Credentials are not found in SSS • BCS connector detects authentication exception from external data source • Default credentials page or custom page • Create your own SS Provider with ISecureStoreProvider

26. BCS Authentication Support Matrix n/a In code In code In code In code In code

27. Authorization in BCS • Rights • Edit – create, delete, update metadata objects • Execute – call external system • Set Permissions – give permissions to other users • Selectable in Clients – accessible to client applications like entity picker • AccessControlListapplies to… • Model • LobSystem • Entity • Method • Set in CA or declaratively in the model XML

28. BCS Search

29. Enabling Your Model For Search • Search Specific Properties • ShowInSearchUI – LOB System • RootFinder – Finder Method and Instance • LastModifiedTimeStampField – Configure for incremental crawling • WindowsSecurityDescriptorField – SpecificFinder instance

30. Summary • Business Connectivity Services (BCS) Primer • Creating BCS Applications • BCS Security • BCS And Search

32. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.