CMIS interface: how it works and why it matters
|
Your content is probably scattered across more systems than you'd like to admit: an ECM platform here, a SharePoint site there, an SAP archive somewhere else. Every one of those systems speaks its own language, and none of them naturally talk to each other.
According to MuleSoft's 2025 Connectivity Benchmark Report, the average enterprise now runs 897 applications, and only 29% of them are integrated. That gap is where content silos live, and it's exactly the problem content management interoperability services were built to solve.
This article breaks down how the CMIS interface works: the protocols behind it, the data model it uses, and how a CMIS client accesses content across otherwise disconnected systems. You'll also see where Doxis fits in, including how it uses CMIS to connect with SAP's cloud landscape.
Key takeaways
- CMIS (Content Management Interoperability Services) is an OASIS standard that lets different content management systems exchange and manage content through a common interface
- It works through three bindings, SOAP, REST, and JSON, and a shared data model built on four object types: documents, folders, relationships, and policies
- A CMIS client gives you centralized access to search, create, edit, and delete content across every connected repository, without a custom integration for each one
- Companies use CMIS to consolidate multiple CMS platforms, connect third-party repositories, migrate off legacy systems, and integrate SAP with non-SAP content stores
- Doxis's CMIS Connector is certified by SAP for the SAP BTP Document Management Service, where it replaces ArchiveLink in cloud environments
What is a CMIS interface?
CMIS stands for Content Management Interoperability Services, a vendor-agnostic standard for connecting DMS, ERP and ECM platforms, and content repositories so they can exchange and manage information through one shared interface. It was developed by OASIS, with version 1.0 released in 2010 and version 1.1 in 2013, backed by vendors including IBM, Microsoft, Adobe, SAP, and Accenture.
How does the CMIS interface work?
A CMIS client sits between the person or application requesting content and the systems where that content lives. Instead of connecting separately to each repository, the client talks to all of them through the same interface, so you can search, create, edit, update, and delete information across multiple platforms as if they were one system.
Two pieces make that possible: the protocols that carry the requests, and the data model that describes what's being requested.
Protocols: SOAP, REST, and JSON bindings
CMIS defines three bindings for how systems communicate:
- SOAP: an XML-based binding for structured, contract-driven communication
- REST: an XML- and web-based binding built on HTTP
- JSON: a lightweight binding that works with RESTful web services
These bindings give every connected platform a shared vocabulary. Regardless of which vendor built the underlying system, requests and responses follow the same structure, so systems exchange content without a custom-built translation layer for each connection.
The CMIS data model: Four object types
Underneath the protocols, CMIS organizes content using a consistent data model built on four base object types:
- Document objects: the actual content stored in a content management system
- Folder objects: the organizational structure that holds documents and other folders
- Relationship objects: associations between two or more objects
- Policy objects: rules applied to content, such as retention or access requirements
Access control lists (ACLs) sit alongside these object types, governing who can see or act on which content. Because every connected system maps its content into this same model, a document created in one platform, say Microsoft SharePoint, can be picked up, understood, and moved into another, like Doxis, without manual reformatting.
How a CMIS client accesses content across systems
Put the protocols and the data model together, and here's what happens: a CMIS client sends a request, using SOAP, REST, or JSON, to a repository. That repository interprets the request against the shared object model and returns the document, folder, or metadata being asked for. The client repeats this against any CMIS-compliant repository, giving you one point of access instead of a dozen separate logins, search bars, and export routines.
How to connect a system using the CMIS interface
Hey Doxi, how do you connect a system using the CMIS interface?
Setting up a CMIS connection follows the same basic sequence regardless of which platforms you're linking. Here's what that looks like in practice, including where a platform like Doxis removes steps rather than adding them.
Step 1: Confirm CMIS compatibility
Check whether both systems support CMIS, and which version. Most modern content management systems and DMS platforms list CMIS 1.0 or 1.1 support in their technical documentation, but the exact binding supported (SOAP, REST, or JSON) can vary by vendor and by deployment. Doxis's own CMIS interface supports all three bindings, so compatibility questions come down to the system on the other end, not Doxis.
Step 2: Choose a binding
Pick the protocol that fits your environment. REST and JSON bindings are lighter weight and easier to work with for cloud and web-based integrations, while SOAP suits systems built around older, contract-driven architectures. For SAP S/4HANA Cloud and SAP BTP specifically, the Doxis CMIS Connector is pre-configured to the binding SAP's Document Management Service expects, so there's no protocol decision to make on that side.
Step 3: Map content to the CMIS data model
Confirm how your existing content maps to CMIS's four object types, documents, folders, relationships, and policies, along with any access control lists that need to carry over. This step is where mismatched metadata or folder structures usually surface, so it's worth doing before you connect anything live. Doxis's content federation capabilities handle this mapping against external repositories, so you can connect a source system's content into Doxis's data model without migrating it first.
Step 4: Configure the client connection
Set up the CMIS client with the repository's endpoint URL, authentication credentials, and the binding you selected in Step 2. Certified connectors, like the Doxis CMIS Connector for SAP BTP, handle most of this configuration out of the box, since the mapping and endpoint setup are already built to the target system's specification. That certification is also why the connection replaces ArchiveLink cleanly for SAP S/4HANA Cloud customers, rather than requiring a parallel setup.
Step 5: Test and validate access
Run a test batch covering search, retrieval, creation, and deletion across both systems before rolling the connection out more broadly. Check that metadata, versioning, and access permissions carry over correctly, since these are the details that are easiest to miss in a rushed setup. With Doxis, this validation happens against a platform that also handles audit-proof archiving and retention, so the same test confirms compliance requirements are met, not just connectivity.
Solving the Archive Challenge in Your SAP S/4HANA Migration
Moving to SAP S/4HANA Cloud? See how ECM and the CMIS interface solve the archiving gap ArchiveLink leaves behind.
Read nowHow companies use CMIS in practice
CMIS shows up most often in four scenarios: bringing multiple content platforms together, connecting outside tools into an existing CMS, replacing legacy SAP archiving in the cloud, and running migrations without downtime.
Consolidating multiple content management systems
Most enterprises run more than one CMS, often down to the department level, and mergers, restructuring, or IT changes multiply that further. Without CMIS, connecting each system means building and maintaining a separate custom interface for every pair of platforms. With CMIS, every system speaks the same protocol, so you integrate once instead of repeatedly. Content federation takes this a step further by linking external repositories into one governed layer without requiring a full migration.
Connecting third-party repositories and tools
Companies also use CMIS to pull external repositories, collaboration tools, and specialized document services, for example, systems used in contract or invoice management, into their core CMS. The result is one searchable, governed content layer instead of pockets of information that only certain teams can reach.
CMIS for SAP: Replacing ArchiveLink in the cloud
For SAP customers, CMIS plays a specific and increasingly important role. SAP's classic ArchiveLink interface was built for on-premises archiving, but in cloud environments like SAP S/4HANA Cloud and SAP Business Technology Platform, CMIS takes over that job. Content is archived and retrieved through the SAP BTP Document Management Service using the CMIS interface, rather than ArchiveLink.
Doxis for SAP reflects this shift directly: the Doxis CMIS Connector is certified by SAP for the SAP BTP Document Management Service, giving you audit-proof, long-term storage for SAP S/4HANA Cloud content without leaving your cloud architecture behind.
Migration and modernization projects
CMIS also acts as a bridge during migration and modernization projects. Content stored on a CMIS server can be accessed by both an old system and a new one at the same time, which supports a gradual, "hot" migration where both platforms run in parallel instead of forcing a hard cutover. The Doxis Consolidation Service applies this same principle to full-scale ECM migrations, moving documents and metadata step by step while legacy systems are gradually retired. The same approach applies when upgrading an existing system with new content or capabilities.
Which software solutions support CMIS?
CMIS support varies by vendor and version, so check a solution's documentation before assuming compatibility. Standard software applications that support the CMIS standard include:
- Doxis Content Services Platform
- IBM Content Manager
- IBM LotusLive Files
- Microsoft SharePoint Server
- SAP HANA Cloud Document Service
Doxis also has a CMIS interface, letting it connect to any compatible platform regardless of vendor, including Microsoft SharePoint Server and the SAP HANA Cloud Document Service.
How Doxis uses the CMIS interface
Doxis is built as a Content Services Platform with an API-first approach, combining REST, CMIS, and dedicated connectors to bring content, process, and compliance capabilities together on one platform. That architecture means CMIS isn't an add-on for Doxis, it's part of how the platform integrates with the rest of your IT landscape from day one.
If you're managing content across SAP, Microsoft 365 and Teams, or other enterprise systems, here's what that gets you with Doxis:
- A CMIS Connector certified by SAP for the SAP BTP Document Management Service, replacing ArchiveLink for SAP S/4HANA Cloud and SAP BTP environments
- Content federation, so you connect external repositories and data sources without a full migration
- A single, centralized access point for documents, metadata, and files stored across every connected system
- Audit-proof archiving that carries versions, context, and relationships through, not just the raw files
- A modular platform, so you add ECM, IDP, or BPM capabilities as your integration needs grow
Doxis is recognized as a Leader in the Gartner® Magic Quadrant™ for Document Management 2026, reflecting the same integration depth that makes CMIS interoperability possible across a genuinely mixed IT environment.
Curious how Doxis could work for your CMIS needs? Get in touch and we'll walk you through it.
Automate Work. Accelerate Business.
Bring together AI, ECM, and workflow automation in one powerful enterprise platform.
FAQs on CMIS interfaces
What does CMIS stand for?
CMIS stands for Content Management Interoperability Services, a vendor-agnostic standard that connects content management systems and repositories so they can exchange and manage content through one interface.
Which systems can a CMIS interface connect?
A CMIS interface connects content management systems, DMS platforms, ERPs, and content repositories with each other, and can integrate third-party tools into an existing CMS. Check each vendor's documentation to confirm CMIS compatibility.
Why do companies need a CMIS interface?
Companies use CMIS to standardize how different platforms exchange content, giving them centralized access to data stored across systems instead of building a separate integration for every pair of platforms.
What protocols does CMIS use?
CMIS communicates through three bindings: SOAP, an XML-based protocol, REST, a web-based protocol built on HTTP, and JSON, a lightweight binding for RESTful services.
How does CMIS help with SAP integration?
In cloud environments like SAP S/4HANA Cloud and SAP BTP, CMIS replaces the older ArchiveLink interface for archiving and retrieving content through the SAP BTP Document Management Service.
Does Doxis support CMIS?
Yes. The Doxis CMIS Connector is certified by SAP for the SAP BTP Document Management Service, and Doxis connects to any CMIS-compliant platform regardless of vendor.
Can CMIS be used for system migrations?
Yes. Because content on a CMIS server can be accessed by both an old and a new system simultaneously, CMIS supports gradual, "hot" migrations where systems run in parallel instead of requiring a hard cutover.
What are the four object types in the CMIS data model?
The four base object types are document objects, folder objects, relationship objects, and policy objects, alongside access control lists (ACLs) that govern who can access specific content.
How can we help you?
+49 (0) 30 498582-0Your message has reached us!
We appreciate your interest and will get back to you shortly.