CMIS + Documentum Web Services

33
CMIS + Documentum Web Services Integrations, Extensions and Mash-Ups... But Which Should You Use When? Ameet Jani 12.11.2009

description

CMIS + Documentum Web Services. Integrations, Extensions and Mash-Ups... But Which Should You Use When? Ameet Jani 12.11.2009. Goal for Today. - PowerPoint PPT Presentation

Transcript of CMIS + Documentum Web Services

Page 1: CMIS + Documentum Web Services

CMIS + Documentum Web Services

Integrations, Extensions and Mash-Ups... But Which Should You Use When?

Ameet Jani

12.11.2009

Page 2: CMIS + Documentum Web Services

Goal for Today

See how Documentum’s web services pulls together CMIS for standards based interoperability and integrations, DFS for building and extending your client applications, and RESTful services for Rich Internet Application mash-ups.

Page 3: CMIS + Documentum Web Services

Overview

• Web Service• Technical Detail of each service

–Roadmap–Examples

• Ideal use case

Page 4: CMIS + Documentum Web Services

About your Presenters

AMEET JANI

Principal Product Manager

The son of Zeus and Hera.

He is also the product manager for Web Services at Documentum, including DFS and CMIS services; He has been with EMC since 2007.

Page 5: CMIS + Documentum Web Services

DOCUMENTUM WEB SERVICES

Enterprise Content Services Overview

Documentum’s existing Web Services API

Rich set of functionality

DOCUMENTUMFOUNDATION

SERVICES

Interoperability standard for ECM

Allows for basic operations on content

CMIS

REST based services

Exposes functionality as Resources

DOCUMENTUMRESTful

SERVICES

Page 6: CMIS + Documentum Web Services

Services Architecture

Content Server

DOCUMENTUM PLATFORM

FILE STORE RDBMS FULL TEXT XML STORE

Documentum Foundation Services & CMIS

Documentum Foundation Classes

Page 7: CMIS + Documentum Web Services

DOCUMENTUM WEB SERVICES

Enterprise Content Services Overview

SOAP/WSDL based

Provides out of the box services to quickly build applications

DOCUMENTUMFOUNDATION

SERVICES

Interoperability standard for ECM

Allows for basic operations on content

Page 8: CMIS + Documentum Web Services

Documentum Foundation Services

Exposes APIs as Web Services

Content Services delivered first

Deconstruct functionality and re-aggregate APIs at higher level

Standards-based interface

Greatly shortens time to develop

Easily content-enable applications

Documentum Foundation Services

Schema Service Data Dictionary Support

Object Servicecreate, update, delete, copy, move,etc.

Version Control Service checkin, checkout, cancelCheckout, etc

Query Service

Search Service supports multiple repositories

Workflow Service startProcess, getProcessInfo, etc

Exposing Documentum Functionality as Services:

Page 9: CMIS + Documentum Web Services

Full Documentum Functionality

Access Control Service create, update, delete, get ACL

Lifecycle Service attach, detach, execute, getLifecycle

Virtual Document Service create, retrieve, addChildren, etc.

Query Store Service saveQuery, loadSavedQuery, etc.

Task Management Service start, stop, release, suspend, etc.

Comment Service create, enum, markRead, markUnread, etc.

Analytics Service analyze

Content Delivery Service publish, ingest, etc

Profile Service (CTS) add, get, remove, update, etc.

Transformation Service transformJob, addJob, deleteJob, etc.

Policy Service apply, remove, getAppliedPolicies, etc.

Electronic Signature Service add, verify

ERP Integration Services executeAction, executeAgent, etc.

Formal Record Service createFormalRecord, declare, etc.

Page 10: CMIS + Documentum Web Services

Documentum Foundation Services are SOAP-based services

DataObject(folderIdentity, "dm_folder");PropertySet properties = new PropertySet();String folderName = "aTestFolder“;properties.set("object_name", folderName);dataObject.setProperties(properties);DataPackage dataPackage = new DataPackage(dataObject);

return objectService.create(dataPackage, operationOptions);

DFS Technology

Page 11: CMIS + Documentum Web Services

What’s Next for DFS?

• Short-term– Administration services– Collaboration services– Search services– XML services– BPM services

• Long-term– “xCP services”– Business services– Easy composition of services

Page 12: CMIS + Documentum Web Services

Ideal DFS Usage Characteristics

• Documentum Foundation Services are ideal for

–System to System integration–Strongly typed languages–Applications that need an explicit contract

• WSDL, policies, security

• Example Applications–Business Process Management

Page 13: CMIS + Documentum Web Services

DOCUMENTUM WEB SERVICES

Enterprise Content Services Overview

SOAP/WSDL based

Provides out of the box services to quickly build applications

Interoperability standard for ECM

Allows for basic operations on content

REST based services

Exposes functionality as Resources

DOCUMENTUMRESTful

SERVICES

Page 14: CMIS + Documentum Web Services

Documentum RESTful Services

• It is a new RESTful HTTP interface to Documentum

• The Documentum REST API builds on the DFS conceptual model and semantics

• It supports XML and JSON resource representation

• Any Language with HTTP and XML or JSON capability could consume the REST API

Page 15: CMIS + Documentum Web Services

RESTful Service Example

Top resource is Repositorieshttp://server/resources/core/repositories.xml

<core:representation><core:repository href="http://server/resources/core/repositories/TaskSpace.xml"> <core:name>TaskSpace</core:name> <core:repositoryType>managed</core:repositoryType> <core:uri>

http://server/resources/core/repositories/TaskSpace.xml </core:uri> <core:objects href="http://server/resources/core/repositories/TaskSpace/objects.xml"/> <core:folders href="http://server/resources/core/repositories/TaskSpace/folders.xml"/> <core:queries href="http://server/resources/core/repositories/TaskSpace/queries.xml"/> <core:types href="http://server/resources/core/repositories/TaskSpace/types.xml"/></core:repository>

</core:representation>

Page 16: CMIS + Documentum Web Services

Documentum RESTful Services Core Resources

RepositoryRepository

ObjectsObjects

ObjectObject

FoldersFolders FolderFolder

UserUser

GroupGroup

RepositoriesRepositories

QueriesQueries

TypesTypes

QueryQuery

RelationshipRelationship

RelationshipsRelationships

UsersUsers

FormatsFormats

RelationshipTypesRelationshipTypes

GroupsGroups

FormatFormat

relationshipTyperelationshipType

TypeType

CheckedoutCheckedout ContentContent

VersionsVersions

Page 17: CMIS + Documentum Web Services

RESTful copies the Internet Linking Model

BankBank

Balance HistoryBalance History

AccountAccount

Internet action follows concept of “linking”

Page 18: CMIS + Documentum Web Services

Documentum RESTful Services

• Today:– “Core” RESTful resources available on Early Access community

on EMC Community– Basic Content Management functionality

• Tomorrow:– Customer feedback to update services– More product functionality exposed as RESTful services

• xCP• BPM

• Important note: Goal is not parity between DFS and REST. Often, these services serve very different purposes

Page 19: CMIS + Documentum Web Services

Ideal RESTful Usage Characteristics

• RESTful Services are ideal for–System to Application integration–Dynamic Languages–Applications that can discover next resource

• Example Applications–Mobile Clients

Page 20: CMIS + Documentum Web Services

DOCUMENTUM WEB SERVICES

Enterprise Content Services Overview

SOAP/WSDL based

Provides out of the box services to quickly build applications

Interoperability standard for ECM

Allows for basic operations on content

CMIS

Page 21: CMIS + Documentum Web Services

Content Management Interoperability Standard

• Web services standard for exchanging content with multiple Enterprise Content Management (ECM) systems

• Oasis standard • currently v0.9 spec

• EMC, IBM, Microsoft founding members

–OpenText, Alfresco, SAP, Oracle, etc invited to join

Tech Pubs Engineering Sales

Page 22: CMIS + Documentum Web Services

CMIS Value

CMIS functionality includes:•Create, Read, Update and Delete•Security

CMIS includes both a SOAP and REST interface for developers

Page 23: CMIS + Documentum Web Services

Ideal CMIS Usage Characteristics

CMIS

Interoperability

Page 24: CMIS + Documentum Web Services

Documentum Services and CMIS

DFS:• Rich security model

•ACLs• Workflows of content stored in Documentum• Collaboration Services• XML• Full Text Search•Compliance•Interactive MediaERP

CMISBasic object svcs

Read, writeBasic security model

Page 25: CMIS + Documentum Web Services

Four Main Use Cases of CMIS

Multi-Repository

Application + ECM

Integration

Build Once, Use Often

Migration

Page 26: CMIS + Documentum Web Services

Four Main Use Cases of CMIS

Multi-Repository

Typical User: Corporate IT

•An organization that has multiple types of repositories•Acquisitions, homegrown ECMs, intra-departmental

•Some content stored in multiple places, need to consolidate into one place

Page 27: CMIS + Documentum Web Services

Four Main Use Cases of CMIS

Typical User: Application Developer

•Combine Content with Business Data

•Example:•Combine Invoice number stored in SAP ERP system with invoice stored in ECM

Application + ECM

Integration

Page 28: CMIS + Documentum Web Services

Four Main Use Cases of CMIS

Typical User: System Integrations (e.g. Capgemini)

•System Integrator builds ECM Solution they want to reuse at many customers, regardless of customer ECM choice

Build Once, Use Often

Page 29: CMIS + Documentum Web Services

Four Main Use Cases of CMIS

Typical User: Documentum Administrator

•Need to migrate content from multiple ECM systems into one

•Any CMIS supported vendor can read content from another CMIS vendor into their local ECM system

Migration

Page 30: CMIS + Documentum Web Services

Documentum usage of CMIS

Content continues to be stored in local CMIS - supported repositories

Content continues to be stored in local CMIS - supported repositories

CMIS AdapterCMIS Adapter

Documentum acts as a “master” repository – a centralized view of all content

Documentum acts as a “master” repository – a centralized view of all content

DOCUMENTUMCLIENT

DOCUMENTUMCLIENT

DCTM

Virtual Content Management uses CMIS to find content in other repositories and put retention rules through Documentum

Page 31: CMIS + Documentum Web Services

Summary

SOAP

• Server based applications

• WSDL is an explicit contract

• Such as messages, operations, bindings, and location of the web service.

• Not restricted to HTTP protocol (applicable for Java/ .NET)

Documentum REST API

• Client application (Requires less client-side software to be written)

• Simple CRUD type of application

• No resource discovery mechanism required (hyperlinks in resources)

SOAP REST

CMIS

Documentum web services layer

CMIS• CMIS is about interoperability • Content collaboration / aggregation; BCS Basic content services (CRUD+ Query)• ISV applications that plug into multiple repositories

Page 32: CMIS + Documentum Web Services

Get Active in the EMC CMA Communities

WHY?Collaborate and share best practices

Network with other innovators across the globe, 24/7Help shape the direction of EMC products

Join Now!!

Page 33: CMIS + Documentum Web Services

Thank you