Ben Robb MVP, SharePoint Server CTO, cScape Ltd Interoperability Overview: All Roads Lead to SharePoint

3 Interoperability Challenges Enabling applications that work together Application Integration Developer Resources Accelerating collaboration, workflow Managing heterogeneous environments Supporting key standards to enable better future interoperability

4 SharePoint 2010 Interoperability

5 UI Interoperability Core Scenarios Great user experience across all common browsers Easier for a web expert to understand Expanded cross-browser support Well-formed HTML/CSS output WCAG 2.0 Core features Cross-browser rich-text editor Firefox open/save integration

User Interface DEMO

7 Identity Interoperability 3 rd party authentication “My company doesn’t use Windows Integrated Authentication on its web sites.” Delegation to back-end systems “I would like to show data from some other server on a SharePoint web page.”

Multi-Signin with Claims

9 Standards

10 Search Interoperability Core Scenarios Query a 3 rd party search engine using SharePoint UI Federate queries to multiple search systems Index content from a range of content repositories

11 OpenSearch Standard (Creative Commons) for syndication and aggregation of search results Syntax for executing queries Results returned in RSS/ATOM + extensions Supported by Microsoft Search Server 2008 Clients: Windows 7, IE, FireFox, SharePoint … Providers: Amazon, Flickr, Wikipedia, SharePoint…

12 OpenSearch Clients

13 Interoperable Indexing Content Indexing via BCS Databases, web services or custom repositories Consistent access to external content SharePoint Designer and Visual Studio Plug-in

Search DEMO

15 Data Interoperability Core Scenarios Display and interact with 3 rd party data using familiar SharePoint UI mechanisms Consume SharePoint data using 3 rd party UI Develop against SharePoint data using standardized data access protocols

16 CMIS Goals Proposed standard for interoperability between Enterprise Content Management (ECM) repositories and applications. Includes a “domain model” and support for 2 protocols: SOAP & REST/Atom. Designed to be mapped onto existing ECM system History Started in October 2006 by IBM, EMC, MSFT. Expanded in 2007 to include: Alfresco, OpenText, Oracle and SAP. Transferred to the OASIS Technical Committee as of 9/10.

17 Conceptual Architecture Disclaimer: Product Plans by individual companies TBD

18 Target Scenarios E-Discovery: Enable e-Discovery applications that can work against any repository, while still leveraging key ECM concepts like object types & metadata, relationships and versioning. Archival: Enable consistent archiving of information from business systems to CMIS-compliant repositories Compound / Virtual Document: Enable consistent modeling, discovery and persistence of compound document relationships for CMIS-compliant repositories

19 3 rd Party Client on CMIS Providers

20 SharePoint Client on CMIS Providers

21 REST Access to SharePoint lists and document libraries RESTful interface over HTTP Uses the ADO.NET Data Services interface conventions Feature rich: retrieve, update, browse data using just URLs and XML/JSON 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 No client required, Visual Studio creates proxies, visualizes schemas, provides LINQ support Sample: GET gt 200

22 External Data Core Scenarios Show LOB data in my SharePoint UI Build end-to-end client+server applications Easily connect custom applications into SharePoint

23 Office Apps DevPlatformDevPlatform Business Intelligence Enterprise Content Mgmt Collaboration Social EnterpriseSearchEnterpriseSearch Web 2.0 DBWCF Web Service LOB SharePoint Design Tools

Data DEMO

25 Investment Areas Extend Office and SharePoint‘s UX and capabilities to External Data and Processes Presentation Read-Write capable connectivity from client and server to Databases, WCF/WebServices and.Net sources Connectivity Integrated tooling experience scales from simple solutions to advanced Pro-Dev apps. Solution packaging, deployment and management. Tooling

26 Storage Interoperability : RBS Store document contents outside SharePoint’s SQL database Using a solution from a storage provider partner BLOB Store X BLOB Store Y BLOB Store Z Content Database SQL Server Config Database

27 SharePoint Interoperability Working end-to-end scenarios SharePoint + 3 rd Party systems All levels of the architecture Interoperability Principles Ensuring Open Connections Data Portability Enhanced Support for Standards Open Engagement

28 SharePoint 2010 Interoperability

29 Summary

30 Resources All resources, Tech Days recordings and decks will be available at:

© 2008 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.