Enterprise Content Management Standards CMIS

3,618 views
3,479 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
3,618
On SlideShare
0
From Embeds
0
Number of Embeds
104
Actions
Shares
0
Downloads
28
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Enterprise Content Management Standards CMIS

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

×