Upload
lucy-riley
View
216
Download
0
Tags:
Embed Size (px)
Citation preview
An Introduction
‣What we are announcing
‣Why is this important to customers? (I.e. the business case)
‣The current standards landscape
‣What is CMIS?o Goalso Target scenarioso Workshopo Timeline
Content Management Interoperability Services Proposed Standard
‣Starting in October 2006, EMC, IBM and Microsoft joined forces to propose the first Web services standard for exchanging content with and between ECM systems.
‣Additional collaborators now include: Alfresco, OpenText, Oracle and SAP
‣We are now announcing that the proposed standard is called the Content Management Interoperability Services (CMIS) and will be registered for public comment with OASIS starting 9/10
‣What we are releasing:‣ Common Domain Model for CM (Data Model, Capabilities)
‣ Bindings: SOAP for System to System, REST/Atom for System to Application
Multiple content repositories and vendor specific systems
‣Discrete business units‣Application specific ECM
solutions‣Mergers and acquisitions
Results‣Stove-piped information ‣Discrete environments‣Multiple investments‣Added costs‣Loss of business flexibility‣ Increased complexity for
developers
ChallengesTech Pubs Engineering Sales
Improved user access to content Increases enterprise effectiveness
‣ Easier for users to get access to the right information at the right time from their application
Reduces application development costs and grows ISV’s addressable market
‣ Develop application once to access CMIS-compliant repositories
Protects customer’s investment in applications and repositories
‣ Developed applications can run against multiple repositories
Propels ECM industry to the next level of growth
‣ Defines a set of standards, technology and interface, that works across multiple vendor and technology providers.
BenefitsTech Pubs Engineering Sales
Migrate content from one system to another. Build/buy one-off connectors to enable interoperability in limited
scenarios. Federation Current standards are not inclusive of all major ECM vendors
We need an open standard that works across heterogeneous systems
Content Management Related Standards
‣Java Content Repository (JSR 170/283)
‣Atom / Atom Publishing Protocol: (APP)
‣Java Portlet Specification (JSR 168), ASP.Net Webparts, Web Services for Remote Portlets (WSRP)
‣WebDAV
‣Other industry standards-related activities‣ iECM Consortium‣ECM Publicly Available Specification (PAS) through British
Standards Institution (BSI)
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
o Enable applications to target one or more ECM repositories uniformly for core content services
‣Easy mapping to existing ECM systemso Expose standard set of APIs for existing capabilities of CM repositorieso Leverage existing content
‣Provide several protocol bindings using the common domain model:
o Simple Object Access Protocol (SOAP)o Representational State Transfer (REST) / ATOM
‣Exploit web technologieso Web 2.0o Internet Scaleo Service-orientationo Resource-orientation
Disclaimer: Product Plans by individual companies TBD
What CMIS is not intended to do
‣ Expose ALL capabilities of an ECM repository or applicationo Integrated ECM suites may still use proprietary
interfaces for “better together” functionality where appropriate.
‣ Standardize designer/admin-type operations, e.g.:o Defining object typeso Controlling security
‣Content Collaboration/ Aggregation:o Allow integration of content from different repositories,
not just presentation/views. o E.g. “My Assigned Tasks/Documents” from multiple systems.
o Allow customers to use the user interface of one application for the content of another.
o Support Mashups and Web 2.0 Technologies
Content Centric Applications (e.g. BPM, multi-channel publishing)o Enable applications that can read or publish content to
any repository as part of a business process, without needing specific connectors for each repository.
‣E-Discovery:oEnable e-Discovery applications that can work
against any repository, while still leveraging key ECM concepts like object types & metadata, relationships and versioning.
‣Archival:oEnable consistent archiving of information from
business systems to CMIS-compliant repositories
‣Compound / Virtual Document:oEnable consistent modeling, discovery and
persistence of compound document relationships for CMIS-compliant repositories
All seven vendors participated: Alfresco, EMC, IBM, Microsoft, OpenText, Oracle and SAP
Achieved Interoperability among the companies, including:◦ IBM Lotus and Microsoft SharePoint clients on
CMIS Providers◦ SAP client on CMIS Providers
Prototypes at Workshop
REST/AtomBinding
Web Service (SOAP)Binding
Consumer Provider Consumer Provider
Alfresco
BEA/Oracle
EMC
IBM
MSFT
OpenText
SAP
Date Event
October 2006 CMIS effort started by IBM, EMC and Microsoft.
July 2007 Version 0.1 of spec completed
August 2008 CMIS Interoperability Workshop
September 2008 Spec transitioned to OASIS
End of year 2009(?) CMIS specification ratified by OASIS
TBD CMIS 1.0 supported in IBM, MS, EMC, other vendors’ products
CMIS Technical Overview
SOAP:◦ Service-oriented binding◦ Uses a CMIS-specific schema.
REST/ATOM:◦ Resource-based binding◦ Leverages the ATOM/APP formats with CMIS-
specific extensions. E.g. Performing an HTTP “get” on a Folder’s URL
returns an ATOM feed of its children, with an extra CMIS XML block for each child’s metadata.
◦ Browse-able by standard ATOM feed readers.
Core objects:◦ Document
May have zero, one or more than one byte-stream in addition to metadata◦ Folder◦ Relationship
A typed relationship between one document or folder to another.
Object Types:◦ Hierarchical “Object Types” define metadata schema of all objects.
Hierarchy:◦ Content is organized into folders
Versioning:◦ Major/minor versioning of Documents◦ Linear versioning model (no “branching” into version trees)
SQL-based query syntax Includes:
◦ Full-text indexing (optional)◦ Returning relevancy scores◦ Property-specific queries (e.g. where
ModifiedDate > 6/11/2007)◦ Wildcards
Authentication is handled by each protocol Authorization context is exposed via an
“AllowableAction” collection on every object◦ Identifies what actions a user can perform, given
their permissions & the object state.
CMIS Repositories can optionally support the following capabilities:◦ Multi-filing/un-filing: Allows documents to be
filed in >1 folder concurrently, or un-filed. Used in applications like case management (where a
single document may be relevant to multiple cases).
◦ Full-text Query support: Allows repositories to support property-only queries.
◦ “SQL Join” Query Support: Allowed repositories to specify whether they support “joining” of query results.
Repository Services◦ getRepositories◦ getRepositoryInfo◦ getTypeDefinition◦ getTypes
Navigation Services◦ getCheckedOutDocs◦ getChildren◦ getDescendants◦ getFolderParents◦ getObjectParents
Policy Services◦ applyPolicy◦ getAppliedPolicies◦ removePolicy
Versioning Services◦ cancelCheckout◦ checkin◦ checkout◦ deleteAllVersions◦ getAllVersions◦ getPropertiesofLatestVersion
Object Services◦ createDocument◦ createFolder◦ createPolicy◦ createRelationship◦ deleteContentStream◦ deleteObject◦ deleteTree◦ getAllowableActions◦ getContentStream◦ getProperties◦ moveObject◦ setContentStream◦ updateProperties
Discovery Services◦ Query
Multi-Filing Services◦ addObjectToFolder◦ removeObjectFromFolder
Relationship Services◦ getRelationships
EMC Client on CMIS ProvidersDo not distribute
Lotus Client on CMIS ProvidersDo not distribute
SharePoint Client on CMIS ProvidersDo not distribute