| CMIS | |
| Genre: | Enterprise content management |
| Extendedfrom: | SOAP |
Content Management Interoperability Services (CMIS) is an open standard that allows different content management systems to inter-operate over the Internet.[1] Specifically, CMIS defines an abstraction layer for controlling diverse document management systems and repositories using web protocols.
CMIS defines a domain model plus bindings that can be used by applications to manipulate content stored in a repository.
CMIS provides a common data model covering typed files and folders with generic properties that can be set or read. There is a set of services for adding and retrieving documents ('objects'). There may be an access control system, a checkout and version control facility, and the ability to define generic relations. Three protocol bindings are defined, one using WSDL and SOAP, another using AtomPub, and a last browser-friendly one using JSON. The model is based on common architectures of document management systems.
The CMIS specification provides an API that is programming language-agnostic, as REST and SOAP are implemented in many languages.
Many of the original contributors to the specification believed [2] a simplified and standardized way to access unstructured content across all vendors would increase the adoption of ECM products, but only if the standard could remain compatible with existing deployed systems, much the way that ODBC Open Database Connectivity did for the relational database market in the 1990s.
The initial work of developing the momentum and use cases that led to the CMIS proposal was conducted by the iECM Initiative[3] sponsored by AIIM. This ongoing project[4] to foster interoperability[5] among ECM systems is supported by the collaborative efforts of governmental, commercial, vendor, and consulting organizations.
Although initiated by AIIM, CMIS is now administered by OASIS, a web standards consortium. Participants in the process include Adobe Systems Incorporated, Alfresco, EMC, FatWire, HP, IBM, Liferay, Microsoft, Nuxeo, OpenText, Oracle, and SAP. The standard is available for public comment at OASIS.
OASIS approved CMIS as an OASIS Specification on May 1, 2010.[6] CMIS 1.1 has been approved as an OASIS specification on December 12, 2012.[7]
The specification is currently approved as OASIS CMIS v1.1 standard.[7]
There are public discussion lists.[8]
The TC was closed on May 9, 2017, and is no longer active.[9]
There is some discussion on the name of CMIS. Some blogs and authors say that it should be named "DMIS",[10] [11] with D for Document since it is more targeted on ECM.
From the CMIS Specification 1.1, page:[12] "[...] this data model does not cover all the concepts that a full-function ECM repository [...] transient entities (such as programming interface objects), administrative entities (such as user profiles), and extended concepts (such as compound or virtual document, work flow and business process, event and subscription) are not included."
A CMIS server stores content, and offers access via the CMIS protocol. Some servers also allow access via other protocols.
| Software | Open source | Notes | |
|---|---|---|---|
| Alfresco 3.3+ | |||
| Cincom ECM 2.1+ CMIS Connector | CMIS interface of Cincom ECM, forked from NemakiWare.[13] | ||
| Day Software CRX 2.1+ | |||
| dotCMS 2.2 | Early commercial editions of dotCMS had CMIS support, however the open source community edition did not. Note that the latest v4.0 edition of dotCMS has removed support for CMIS entirely. | ||
| Fabasoft | Provides extensions to the core CMIS specification to support "aspects"[14] | ||
| HP Autonomy Interwoven Worksite 8.5 | |||
| IBM Content Manager On Demand 9.0+ | |||
| IBM Connections Files 3.0 | Only documents are accessible via CMIS, other content types are inaccessible. | ||
| IBM LotusLive Files | |||
| IBM QuickFile[15] | |||
| IBM Lotus Quickr 8.5 Lists | Only data lists are accessible via CMIS, other content types are inaccessible. | ||
| LogicalDOC 6.5.1+[16] | |||
| Magnolia (CMS) 4.5[17] | |||
| Microsoft SharePoint Server[18] [19] | CMIS 1.0 is supported out-of-the-box in SharePoint Server 2013. It requires installation of the Administration Toolkit in SharePoint Server 2010. Not available in Foundation version.[20] | ||
| Nuxeo Platform 5.5+[21] | |||
| O3Spaces 3.2+ | |||
| OpenCms 8.5[22] | |||
| OpenKM 6.3+[23] | |||
| OpenText | Since ECM Suite 2010. Implemented through a CMIS Connector above Enterprise Library Services 10.2.0. | ||
| OpenText Documentum[24] 7.x | |||
| OpenWGA 5.2+ | |||
| Oracle Webcenter Content | Content Management REST Service Developer's Guide. | ||
| PTC Windchill | |||
| SAP HANA Cloud Document Service | SAP HANA Cloud Platform Documentation. | ||
| Surround SCM 2011.1 |
Each CMIS server declares a set of capabilities. For instance, servers that allow documents to be filed in different places declare the capability "Multifiling". This mechanism allows clients to interact differently with servers that support or don't support a particular operation.
Some server products allow certain capabilities to be disabled or enabled by configuration. the table below lists maximum capabilities.
| Server | ACL | AllVersions Searchable | Changes | ContentStream Updatability | Get Descendants | Get FolderTree | Multifiling | PWC Searchable | PWC Updatable | Query | Renditions | Unfiling | Version Specific Filing | Join | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Acropolis | |||||||||||||||
| Alfresco | |||||||||||||||
| Ceyoniq Technology GmbH, nscale CMIS Connector | |||||||||||||||
| Chemistry InMemory Server | |||||||||||||||
| eXo Platform[25] | |||||||||||||||
| IBM FileNet Content Manager[26] | |||||||||||||||
| IBM Content Manager | |||||||||||||||
| IBM Content Manager OnDemand | |||||||||||||||
| ISIS Papyrus WebArchive | |||||||||||||||
| NemakiWare[27] | |||||||||||||||
| Nuxeo | |||||||||||||||
| OpenText | |||||||||||||||
| OpenText Documentum | |||||||||||||||
| Laserfiche |
A CMIS server library allows developers to create CMIS server applications.
| Software | Technology | Open source | |
|---|---|---|---|
| NCMIS | .NET | ||
| OpenCMIS Server Framework (part of Apache Chemistry) | Java | ||
| VB.CMIS | .NET |
A CMIS client application typically allows users to browse, read and modify content.
| Software | Technology | Open source | Notes | |
|---|---|---|---|---|
| Atlassian Confluence + Crowd 3.5+/2.2.2+ | Java | Access, list, display, edit, upload and delete Enterprise Alfresco files from Confluence. | ||
| Connect-CMIS[28] (Connector in Pegasystems Inc. Pega 7) | Pega 7 | Allows for connectivity to any CMIS compliant server from Pega 7 | ||
| Drupal 7.x and 8.x[29] | PHP | Can be configured as a CMIS browser | ||
| Hippo CMS[30] | Java | Can be configured as a CMIS browser | ||
| HP Exstream LAL | Java | Framework to connect Live documents with CMIS repositories | ||
| LibreOffice 4.0[31] | C++ | |||
| Liferay 6.1[32] | Java | Synchronizes Liferay's document repository with CMIS servers | ||
| TYPO3[33] | PHP | |||
| WordPress[34] | PHP | Can be configured as a CMIS browser |