The Point Of The Content Interoperability Services (CMIS) Standard

The Point of the Content Interoperability Services (CMIS) Standard What Problems Does CMIS Solve?

You’ve probably heard of CMIS…

C ontent

M anagement

I nteroperability

S ervices

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.

… 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

… and been subjected to some hype… No More Silos!!!

… but you’ve wondered about the real-world application of CMIS.

Wonder No Longer There are 3 fundamental Use Cases (at least!)

#1: Repository to Repository (R2R)

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

For example, publishing systems that output to the web as one medium 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

Content Repository CMIS Interface Content Repository CMIS Interface

#2: Application to Repository (A2R)

What Types of Applications are we Talking About Here?

There are several types of Content Applications, three of them are…

Collaboration/Enterprise 2.0 Applications

Enterprise Software Applications

Content Enabled Vertical Applications (CEVAs)

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!”

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

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

In all cases, it is using the best content application for the job against a shared Content Management system... …not shuffling content between systems

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

…you have this. HR System: Resumes, Offer Letters CRM System: Proposals, Resumes Collaboration System: Proposal, Deliverables Content Repository CMIS Interface

#3: Federated Repositories

What is a Federated Repository?

Not This!! Content Repository

Federated repositories is interacting with multiple repositories as if they were one repository. Content Repository Content Repository Content Repository Content Repository Search Manage

Federated Example: iECM Federated Search 1) User conducts search iECM CMIS Search Federator (California, US) Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface

Federated Example: iECM Federated Search 1) User conducts search iECM CMIS Search Federator (California, US) 2) Federator sends the request out Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface

Federated Example: iECM Federated Search 1) User conducts search iECM CMIS Search Federator (California, US) 2) Federator sends the request out 3) The repositories execute the search and return results Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface

Federated Example: iECM Federated Search 1) User conducts search 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 Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface

Federated Example: iECM Federated Search 1) User conducts search 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 Documentum Repository (Amazon Cloud) CMIS Interface Alfresco Repository (United Kingdom) CMIS Interface Nuxeo Repository (France) CMIS Interface

So we covered three top-level CMIS usage scenarios Federated Repositories Repository to Repository Application to Repository

Hungry for More?