This section consists of the following main topics:
Required nodetypes and namespaces in JCR
Introduction to the mandatory configuration for JCR to work correctly.
Authenticator and organization service configuration
Overall introduction to configuration of authenticator and organization service.
Full provision of CMIS and index, such as query capabilities, configuration, index atomicity and durability.
To expose Content drives to the CMIS repositories, you must make a special extension of CmisRegistry.
To make the org.exoplatform.ecms.xcmis.sp.DriveCmisRegistry typical component, do as follows:
<component>
<type>org.exoplatform.ecms.xcmis.sp.DriveCmisRegistry</type>
<init-params>
<!-- Disabled by default. Uncomment if you need query support in CMIS. -->
<!-- value-param>
<name>indexDir</name>
<value>${gatein.jcr.index.data.dir}/cmis-index${container.name.suffix}</value>
</value-param-->
<value-param>
<name>exo.cmis.renditions.persistent</name>
<value>true</value>
</value-param>
<values-param>
<name>renditionProviders</name>
<description>Redition providers classes.</description>
<!-- <value>org.xcmis.renditions.impl.PDFDocumentRenditionProvider</value> -->
<value>org.xcmis.renditions.impl.ImageRenditionProvider</value>
</values-param>
</init-params>
</component>
Where configuration parameters include:
indexDir: the directory where the lucene index will be placed. It is disabled by default.
exo.cmis.renditions.persistent: indicates if a rendition of the document (thumbnails) should be persisted in the JCR. The allowed value are true or false.
renditionProviders: a set of FQN of classes which can be used as Rendition Providers. Classes which implement the org.xcmis.spi.RenditionProvider interface used to preview the CMIS objects (thumbnails).
In most cases, it is not required to change anything in the xCIMIS configuration. In case of any change of the indexer storage location, do not comment the indexDir value parameter and point it to the actual location.