5.3. eXo CMIS add-on and configuration


You are looking at documentation for an older release. Not what you want? See the current release documentation.

eXo CMIS add-on is built on the top of xCMIS embedded in eXo Platform to expose the Content drives as the CMIS repositories. The CMIS features are implemented as a set of components deployed on the eXo Container using XML files to describe the service configuration.


SOAP protocol binding is not implemented in eXo CMIS add-on.

See how eXo CMIS works in the figure below.

The Content drives exposure is implemented as a Content storage provider to the xCMIS SPI. The storage provider uses mappings from the Content's ManageDriveService to actual JCR nodes. AtomPub bindings make Content structure available via CMIS standard API.


The getRepositories service endpoint is: http://localhost:8080/rest/private/cmisatom.


You do not need to configure anything to make it work, unless you want to enable CMIS index and search.

The configuration is done in ecm-xcmis-extension.war!/WEB-INF/conf/xcmis-configuration/xcmis-configuration.xml.

The following component - org.exoplatform.ecms.xcmis.sp.DriveCmisRegistry that extends CmisRegistry - is used to expose Content drives to the CMIS repositories:

        <!-- Disabled by default. Uncomment if you need query support in CMIS. -->
        <!-- value-param>
            <description>Redition providers classes.</description>
            <!-- <value>org.xcmis.renditions.impl.PDFDocumentRenditionProvider</value> -->


In most cases, it is not required to change anything in the xCMIS configuration. In case of any change on the indexer storage location, uncomment the indexDir value parameter and point it to the actual location.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus