Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Stambia Data Integration allows to work with the Content Management Interoperability Services (CMIS) standard, that is used to manage content management systems documents and folders.

A CMIS Metadata is available to reverse all the Documents, Folders and Relationships Types that can then be used in mappings to perform operations on the CMIS server.

  • Stambia DI Designer S18.2.0 or higher
  • Stambia DI Runtime S17.3.0 or higher


Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

This component may require a dedicated license.

Please contact the Stambia support team if you have any doubt and if you need to use it in a production environment.



You can find below the necessary resources to work with this Component in Stambia DI

Name Description Download
Component resources You can find in download section the Component resources. Component resources download


Supported features

You can find bellow an overview of what Stambia can do with CMIS servers

Name Description

The following CMIS objects can be reversed automatically in a CMIS Metadata:

  • Document Types
  • Folder Types
  • Relationship Types
  • Secondary Types
Document Operations

The following operations can be performed on CMIS documents:

  • Insert
  • Update
  • Upsert
  • Delete
  • DeleteInsert
  • Get
  • Rename
  • Move
Folder Operations

The following operations can be performed on CMIS Folders:

  • Insert
  • Update
  • Upsert
  • Delete
  • DeleteInsert
  • DeleteTree
  • Get
  • Rename
  • Move
Relationships Relationships can be created between two CMIS Documents

All the operations are performed directly on the CMIS server

The sent Documents are defined on the Mappings, by using a relative or absolute path to the physical files

After each CMIS invocation, the resulted Document/Folder properties can be stored in Rdbms

CMIS Properties

The CMIS Properties of the Documents and Folders can be defined in the Mappings during Integrations

They can moreover be retrieved after each CMIS invocation to be stored in Rdbms

CMIS Object Id The CMIS Object Id, identifying uniquely the Documents and Folders, can be used for getting or updating Document and Folders.
CMIS Queries

The CMIS query language can be used when getting Documents or Folders.

This allows to retrieve a filtered list of Documents or Folders.




Suggest a new Article!