320 likes | 338 Views
Explore challenges and solutions for enabling applications to work harmoniously in SharePoint 2010 environment, including identity management, search interoperability, data access, and integration with third-party systems. Learn about core scenarios, search functionalities, and data interoperability methodologies.
E N D
Interoperability Overview:All Roads Lead to SharePoint Ben Robb MVP, SharePoint Server CTO, cScape Ltd
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
SharePoint 2010 Interoperability Identity UI Platform Search Data Access Storage External Data RBS BCS REST CMIS Open Search HTML Standards Claims
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 UI
DEMO User Interface
Identity Interoperability • 3rd 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.” Identity
Multi-Signin with Claims Identity
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 • How to request and receive security tokens • SAML Token 1.1 • XML vocabulary used to represent claims in an interoperable way Identity
Search Interoperability • Core Scenarios • Query a 3rd party search engine using SharePoint UI • Federate queries to multiple search systems • Index content from a range of content repositories Search
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… Search
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 Search
Data Interoperability • Core Scenarios • Display and interact with 3rd party data using familiar SharePoint UI mechanisms • Consume SharePoint data using 3rd party UI • Develop against SharePoint data using standardized data access protocols Data
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. Data
Conceptual Architecture Data Disclaimer: Product Plans by individual companies TBD
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 Data
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 http://myserver/_vti_bin/listdata.svc/ConferenceSessions?$filter=Level gt 200 Data
External Data • Core Scenarios • Show LOB data in my SharePoint UI • Build end-to-end client+server applications • Easily connect custom applications into SharePoint
Business Connectivity Services Office Apps BCS Client Runtime SharePoint Design Tools SharePoint Designer Enterprise Search Dev Platform Business Intelligence Enterprise Content Mgmt Collaboration Social External Lists Visual Studio External Content Types Business Data Connectivity LOB Web Service WCF DB Web 2.0
DEMO Data
Storage Interoperability : RBS • Store document contents outside SharePoint’s SQL database • Using a solution from a storage provider partner SharePoint Object Model Provider API SQL Server Relational Access SQL RBS Client Library RBS Maintainer Provider Library X Provider Library Y Provider Library Z Provider Library Content Database Config Database BLOB Store X BLOB Store Y BLOB Store Z
SharePoint Interoperability • Working end-to-end scenarios • SharePoint + 3rd Party systems • All levels of the architecture • Interoperability Principles • Ensuring Open Connections • Data Portability • Enhanced Support for Standards • Open Engagement
SharePoint 2010 Interoperability Identity UI Platform Search Data Access Storage External Data RBS BCS REST CMIS Open Search HTML Standards Claims
Resources • All resources, Tech Days recordings and decks will be available at: www.microsoft.com/uk/techdays
© 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.