EMC World 2009 - Standards: CMIS


Published on

An overview of the CMIS standard and of the AIIM Demo put together by the iECM committee. This presentation was given by Karin Ondricek of EMC and Laurence Hart of AIIM and Washington Consulting, Inc.

Published in: Technology
1 Comment
No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • EMC World 2009 - Standards: CMIS

    1. 1. Enterprise Content Management Standards: CMIS Karin Ondricek Group Manager, Product Marketing Laurence Hart AIIM iECM Committee Member
    2. 2. The Case for Content Interoperability <ul><li>Multiple Content Repositories </li></ul><ul><li>Discrete business units </li></ul><ul><li>Application specific ECM solutions </li></ul><ul><li>Mergers and acquisitions </li></ul><ul><li>Results </li></ul><ul><li>Stove-piped information </li></ul><ul><li>Discrete environments </li></ul><ul><li>Multiple investments </li></ul><ul><li>Added costs </li></ul><ul><li>Loss of business flexibility </li></ul><ul><li>Increases complexity for developers </li></ul>Challenges Tech Pubs Engineering Sales
    3. 3. Implications <ul><li>Difficult for enterprise to reuse/aggregate content </li></ul><ul><li>Expensive for ISV to address repositories from multiple vendors </li></ul><ul><li>Difficult for users to access content from other sources </li></ul><ul><li>ECM isolation limits ECM adoption </li></ul>Needed: An interoperability standard to make content accessible from any source.
    4. 4. Content Management Interoperability Services <ul><li>A Web-based, protocol-layer interface to enable applications to interoperate with disparate content repositories </li></ul><ul><li>Provide content management functionality that can be readily mapped to most repositories </li></ul><ul><ul><li>A “common denominator” interface; not a full-function ECM interface </li></ul></ul>CMIS Provides Standards-based Content Management
    5. 5. CMIS Target Scenarios <ul><li>Content Collaboration/ Aggregation: </li></ul><ul><ul><li>Allow integration of content from different repositories, not just presentation/views </li></ul></ul><ul><ul><ul><ul><li>E.g. “My Assigned Tasks/Documents” from multiple systems. </li></ul></ul></ul></ul><ul><ul><li>Allow customers to use the user interface of one application for the content of another </li></ul></ul><ul><ul><li>Support Mashups and Web 2.0 Technologies </li></ul></ul><ul><li>Content Processing Applications: </li></ul><ul><ul><li>Read or publish content to any repository as part of a business process, without specific connectors </li></ul></ul>
    6. 6. CMIS Goals <ul><li>A standard for sharing information stored in disparate repositories that is designed to: </li></ul><ul><li>Ensure interoperability for people and for applications among multiple content repositories across all platforms </li></ul><ul><ul><ul><li>Enable applications to target one or more ECM repositories uniformly for core content services </li></ul></ul></ul><ul><li>Easy mapping to existing ECM systems </li></ul><ul><ul><ul><li>Expose standard set of APIs for existing capabilities of CM repositories </li></ul></ul></ul><ul><ul><ul><li>Leverage existing content </li></ul></ul></ul>
    7. 7. The current specification contains… <ul><li>An abstract domain model </li></ul><ul><ul><li>A simple data model (typed objects, versioning, …) </li></ul></ul><ul><ul><li>A set of core services (CRUD, query, navigation, …) </li></ul></ul><ul><li>Two protocol bindings </li></ul><ul><ul><li>Simple Object Access Protocol (SOAP) / WSDL </li></ul></ul><ul><ul><li>Representational State Transfer (REST) / ATOM </li></ul></ul><ul><li>And exploits web technologies </li></ul><ul><ul><li>Web 2.0 </li></ul></ul><ul><ul><li>Internet Scale </li></ul></ul>
    8. 8. CMIS Non-Goals <ul><li>Expose ALL capabilities of an ECM repository or application </li></ul><ul><ul><li>Integrated ECM suites may still use proprietary interfaces for “better together” functionality where appropriate. </li></ul></ul><ul><li>Standardize designer/admin-type operations, e.g.: </li></ul><ul><ul><li>Defining object types </li></ul></ul><ul><ul><li>Controlling security </li></ul></ul>
    9. 9. The Case for Content Interoperability <ul><li>Improves user access </li></ul><ul><li>Users do not require unique applications to access each repository </li></ul><ul><li>Improve process across functional boundaries </li></ul><ul><li>End users don’t require specific applications </li></ul><ul><li>Speeds application development and deployment </li></ul><ul><li>Develop application once to access all repositories </li></ul>Benefits Tech Pubs Engineering Sales
    10. 10. CMIS within the Documentum API Portfolio Interop / Integration What are you trying to accomplish? Build / Customize CMIS
    11. 11. Who is Driving CMIS? <ul><li>Need identified by iECM </li></ul><ul><li>Initial proposal drafted by EMC, IBM & Microsoft </li></ul><ul><ul><li>Reviewed by Alfresco, Open Text, Oracle, SAP </li></ul></ul><ul><ul><li>All built early prototype to validate the design, and tested interoperability among them. </li></ul></ul><ul><ul><li>Draft was unveiled in Sep 2008, and submitted to OASIS </li></ul></ul><ul><li>The OASIS CMIS TC was formed in Nov ‘08 </li></ul><ul><ul><li>20+ vendors are participating </li></ul></ul><ul><ul><li>Aggressive working timeline for v1 </li></ul></ul>
    12. 12. Status Update <ul><li>v0.61 spec is available </li></ul><ul><li>Technical Committee working materials are publicly accessible </li></ul><ul><li>Targeting public review this summer </li></ul><ul><li>Targeting v1.0 end of year or early next year </li></ul>
    13. 13. AIIM iECM Demo <ul><li>Organized by the AIIM iECM Committee </li></ul><ul><ul><li>Thomas Pole, Chair </li></ul></ul><ul><ul><li>Betsy Fanning, AIIM Director of Standards </li></ul></ul><ul><ul><li>Project 2 months before the AIIM Conference </li></ul></ul><ul><li>Search Federator Application </li></ul><ul><ul><li>Development led by Laurence Hart (CMIS Federator) and Thomas Pole (User Interface) </li></ul></ul><ul><ul><li>Use CMIS (Web Services binding) to query/access disparate, geographically distributed vendor repositories </li></ul></ul><ul><li>Content </li></ul><ul><ul><li>Several issues of AIIM E-DOC Magazine, Infonomics Magazine, and vendor material </li></ul></ul><ul><ul><li>Spread across repositories </li></ul></ul><ul><li>Participating vendors </li></ul><ul><ul><li>Alfresco </li></ul></ul><ul><ul><li>EMC Corp </li></ul></ul><ul><ul><li>Nuxeo </li></ul></ul>
    14. 14. How does it work? CMIS Search Federator (California, US) AIIM iECM’s Browser-Based Search User Interface (.NET) Alfresco Repository (United Kingdom) CMIS Implementation Documentum Repository (Amazon Cloud) CMIS Implementation Nuxeo Repository (France) CMIS Implementation
    15. 15. Challenges Building the Demo <ul><li>Hosting Challenges </li></ul><ul><ul><li>Federator hosting service </li></ul></ul><ul><ul><li>Vendor server hosting </li></ul></ul><ul><li>Multiple Firsts </li></ul><ul><ul><li>First SOAP-Based CMIS Application </li></ul></ul><ul><ul><li>First Multi-Vendor CMIS Application </li></ul></ul><ul><ul><li>The 80/20 rule </li></ul></ul><ul><li>Two Months to do Everything </li></ul><ul><ul><li>Head start from Craig Randall </li></ul></ul><ul><ul><li>Craig’s and this application on ECM Developer Network </li></ul></ul><ul><li>Only Possible with CMIS </li></ul><ul><ul><li>Most technical challenges weren’t CMIS related </li></ul></ul><ul><ul><li>Nuxeo connector only took one hour to add </li></ul></ul>