Enterprise Content Management Standards CMIS

1© Copyright 2009 EMC Corporation. All rights reserved.

Enterprise Content Management Standards: CMIS


The Case for Content Interoperability

Multiple Content Repositories Discrete business units Application specific ECM solutionsMergers and acquisitionsResults Stove-piped information Discrete environmentsMultiple investments Added costs Loss of business flexibility Increases complexity for

developers

ChallengesTech Pubs Engineering Sales


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.


CMIS Provides Standards-based Content Management

Content Management Interoperability Services

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


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


CMIS Goals

A 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


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


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


The Case for Content Interoperability

Improves user accessUsers do not require unique

applications to access each repository

Improve process across functional boundaries End users don’t require specific

applicationsSpeeds application

development and deploymentDevelop application once to

access all repositories

BenefitsTech Pubs Engineering Sales


CMIS within the Documentum API Portfolio

Interop / Integration

What are you trying to accomplish?

Build / Customize


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


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


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/

http://wordofpie.com/


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


How does it work?

CMIS Search Federator (California, US)

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


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

Enterprise Content Management Standards CMIS

Technology

Transcript of Enterprise Content Management Standards CMIS