The Point Of The Content Interoperability Services (CMIS) Standard
18 likes12,938 views
The document discusses the Content Management Interoperability Services (CMIS) standard and how it addresses interoperability between content management systems. It describes three main use cases for CMIS: 1) allowing content repositories to interface with each other directly, 2) enabling applications to interface with content repositories, and 3) facilitating federated searching across multiple repositories. Each use case is explained in 1-2 sentences with examples provided. The document concludes by providing additional resources for learning more about CMIS.
The Point Of The Content Interoperability Services (CMIS) Standard
- 1. The Point of the Content Interoperability Services (CMIS) Standard What Problems Does CMIS Solve?
- 2. You’ve probably heard of CMIS… Content Management Interoperability Services Defines a domain model and set of bindings, such as Web Service and REST/Atom, that can be used by applications to work with one or more Content Management repositories/systems.
- 3. …heard about CMIS’s history… • Need identified by AIIM’s iECM Committee • Initial proposal drafted by EMC, IBM & Microsoft – Reviewed by Alfresco, Open Text, Oracle, SAP – Draft was unveiled in Sep 2008, and submitted to OASIS • The OASIS CMIS TC was formed in Nov ‘08 • Targeting public review early fall ‘09 • Targeting v1.0 early 2010
- 4. …and been subjected to some hype… No More Silos!!!
- 5. …but you’ve wondered about the real-world application of CMIS.
- 6. Wonder No Longer There are 3 fundamental Use Cases (at least!)
- 7. #1: Repository to Repository (R2R)
- 8. There are times you want to talk directly between content repositories • Publish a document from one system into another • Manage records from one centralized system
- 9. For example, publishing systems that output to the web as one medium Content Repository CMIS Interface Content Repository CMIS Interface 1) Create a document. 2) Publish Document to WCM System. 3) Document is integrated into website and published. *Also known as a “CMS” in the Web Content Management world Publishing: • Whitepapers • Official Guidelines • Reports Content: • XML • PDF
- 10. #2: Application to Repository (A2R)
- 11. What Types of Applications are we Talking About Here?
- 12. There are several types of Content Applications, three of them are… • Collaboration/Enterprise 2.0 Applications • Enterprise Software Applications • Content Enabled Vertical Applications (CEVAs)
- 13. First, some Collaboration/ Enterprise 2.0 Applications • SharePoint as an interface, not repository • Existing Enterprise 2.0 Applications (Telligent Community, Jive SBS, CenterStage, Beehive) • New CMIS Interfaces “One CMIS Interface to Rule Them All!”
- 14. Let us not forget traditional Enterprise Software Applications • Think of those massive Enterprise 1.0 Applications – Business Process Management (BPM) – Customer Relationship Management (CRM) • They are full of content that needs to be in multiple places and collaborated upon
- 15. And finally, the Content Enabled Vertical Applications (CEVAs) • What is a CEVA? – Electronic Medical Records – Case Management System – Correspondence Tracking System • Vendors with domain expertise build the applications with the business rules and plug into an ECM system
- 16. In all cases, it is using the best content application for the job against a shared Content Management system... …not shuffling content between systems
- 17. Instead of this… CRM Content Repository HR System: Resumes, Offer Letters CRM System: Proposals, Resumes Collaboration System: Proposal, Deliverables Project Content Repository HR Content Repository Resumes Proposals
- 18. …you have this. Content Repository CMIS Interface HR System: Resumes, Offer Letters CRM System: Proposals, Resumes Collaboration System: Proposal, Deliverables
- 20. What is a Federated Repository?
- 22. Federated repositories is interacting with multiple repositories as if they were one repository. Content Repository Content Repository Content Repository Content Repository Search Manage
- 23. Federated Example: iECM Federated Search 1) User conducts search Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface iECM CMIS Search Federator (California, US) iECM CMIS Search Federator (California, US)
- 24. Federated Example: iECM Federated Search 1) User conducts search Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface iECM CMIS Search Federator (California, US) iECM CMIS Search Federator (California, US) 2) Federator sends the request out
- 25. Federated Example: iECM Federated Search 1) User conducts search Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface iECM CMIS Search Federator (California, US) iECM CMIS Search Federator (California, US) 2) Federator sends the request out 3) The repositories execute the search and return results
- 26. Federated Example: iECM Federated Search 1) User conducts search Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface iECM CMIS Search Federator (California, US) iECM CMIS Search Federator (California, US) 2) Federator sends the request out 4) Federator merges the results 3) The repositories execute the search and return results
- 27. Federated Example: iECM Federated Search 1) User conducts search Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface iECM CMIS Search Federator (California, US) iECM CMIS Search Federator (California, US) 2) Federator sends the request out 5) User reviews the results 4) Federator merges the results 3) The repositories execute the search and return results
- 28. So we covered three top-level CMIS usage scenarios Federated Repositories Repository to Repository Application to Repository
- 29. Hungry for More? • OASIS CMIS Technical Committee – http://www.oasis-open.org/committees/tc_home.php?wg_abbrev =cmis#technical • CMIS Developer Resources – http://www.cmisdev.org/cmis/ • The iECM Demo – The story behind it: http://wp.me/p4OLk-7g – The code behind it: http://wp.me/p4OLk-8u • CMIS SQL with Great Description of CMIS – http://www.open-source-ecm.com/2009/08/cmis-tutorial-cmis-sql.html
- 30. Thanks for Watching Pester Me on Twitter with Comments @piewords