CMIS interface: A standard for seamless content management integration

CMIS stands for Content Management Interoperability Services—a vendor-agnostic standard primarily used as an interface for integrating content from multiple content management systems (CMS) including e.g. DMS, ERP and ECM platforms. The CMIS interface can also integrate archives or directories used for managing data, known as content repositories.

The standard was developed by the Organization for the Advancement of Structured Information Standards, or OASIS for short. Version 1.0 was released in 2010, followed by Version 1.1 in 2013, with leading software vendors including IBM, Microsoft, Adobe, SAP and Accenture participating in the development process.

Today, the CMIS interface is intended as a framework for enabling content to be accessed, edited and managed across multiple platforms. A CMIS client gives centralized access to all files, documents, metadata and other information stored on connected platforms, so you can search, create, edit, update and delete information across systems simultaneously.

Protocols unify the language

Unified language is the key to getting different platforms to talk together, and that’s what the CMIS interface does. It’s based on so-called protocols or bindings:

• SOAP: XML-based binding
• REST: XML- and web-based binding that builds on HTTP
• JSON: JSON-based binding that works with RESTful web services

Via these API technologies, platforms can communicate in a standardized, entirely vendor-agnostic format.

Four object types in CMIS

API-based document-sharing works based on a simple data model, which defines four base object types:

• Document objects: Content stored in a CMS
• Folder objects: Organizational structures of documents and folders in the CMS
• Relationship objects: Associations between objects
• Policy objects: Applied policies

Access control lists, or ACLs, are also a type of object and control who can access which content.

These base object types are all interrelated. In other words, the objects know each other and can talk together. For instance, you can seamlessly transfer a document created in Microsoft SharePoint to Doxis via the CMIS interface.

The functions of a CMIS interface offer several advantages:

Interoperability through standardization

The CMIS interface unifies the language used by different software platforms, allowing distributed multi-vendor content solutions to talk together and interact. Simply put, it’s an abstraction layer for controlling multiple systems. This form of standardization is the basis for interoperable data exchanges.

More efficient processes

Seamless interoperability speeds up company-wide business processes. A CMIS interface unifies access to the entire content management system IT infrastructure, tearing down content silos and increasing end-to-end process efficiency.

Flexible to use

New systems connect seamlessly with existing IT infrastructure via the CMIS interface. The unified standard eases integration, in turn reducing implementation and development costs.

Not only that, but rather than choosing software based on integration capabilities, you can focus entirely on the value added—i.e. the functions.

Companies use the CMIS standard with the goal of unlocking content management capabilities across all platforms and centralized access to the information stored there.

Here are some use cases:

Integrate multiple CMS platforms

Most companies use more than one CMS, and it’s not uncommon to find separate platforms right down even to department level. Mergers, restructuring or changes to IT infrastructure can all spur companies to consolidate the contents of their disparate CMS solutions. Without CMIS, they would need to develop a special interface for every system. With CMIS, they seamlessly integrate all systems.

Integrate third-party systems into CMS

Companies also use the CMIS interface to integrate third-party systems—repositories, collaboration tools and other document management services used for contract management or invoice management purposes—into their CMS.

Migration and modernization

Finally, companies use the CMIS interface to help modernize their IT systems. For example, in migration projects, CMIS acts as a link between an old content management system (CMS) and a new one, as content is stored on the CMIS server. This allows for a gradual migration of your software while both systems run side by side, which is essential for a smooth "hot migration." The same method can also be used to upgrade existing systems with new content or features.

To find out if a specific solution supports CMIS, consult the documentation or resources provided by its developer. Below are examples of standard software applications that support integration with the CMIS standard:

• IBM Content Manager
• IBM LotusLive Files
• Microsoft SharePoint Server
• SAP HANA Cloud Document Service

Doxis, too, has a CMIS interface that will connect with compatible software, regardless of vendor. It means you can seamlessly connect Doxis to the Microsoft SharePoint Server or the SAP HANA Cloud Document Service.

In wrap-up, CMIS interfaces standardize how you access different content management systems, such as DMS platforms, enabling seamless integration—like connecting your SAP platform with Doxis. This creates smoother information flows across your company, between departments, and across platforms. The result? Improved collaboration company-wide and reduced costs through better data availability.

Curious how Doxis could work for your CMIS needs? Get in touch—we’d be happy to talk it through.

FAQs on CMIS interfaces