2.1. Basic configuration

JCR configuration
Details of the JCR configuration, including Repository, Workspace, Value storage plugin, Initializer, Cache, Query Handler and Lock Manager.
JCR configuration persister
Instructions on how to configure and customize the JCR persister.
JDBC data container configuration
Information about configuration of JDBC data container.
Frequently asked questions
Questions and their answers related to commonly basic configurations, such as Lucene spellchecker, spellchecker results, Help application, and more.

The JCR service configuration (for example, Repository service) that can be found in jcr-configuration.xml looks like the following:


<component>

  <key>org.exoplatform.services.jcr.RepositoryService</key>

  <type>org.exoplatform.services.jcr.impl.RepositoryServiceImpl</type>

</component>

<component>

  <key>org.exoplatform.services.jcr.config.RepositoryServiceConfiguration</key>

  <type>org.exoplatform.services.jcr.impl.config.RepositoryServiceConfigurationImpl</type>

  <init-params>

    <value-param>

      <name>conf-path</name>

      <description>JCR repositories configuration file</description>

      <value>war:/conf/jcr/repository-configuration.xml</value>

    </value-param>

    <value-param>

      <name>max-backup-files</name>

      <value>5</value>

    </value-param>

    <properties-param>

      <name>working-conf</name>

      <description>working-conf</description>

      <property name="persister-class-name" value="org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister" />

      <property name="source-name" value="${gatein.jcr.datasource.name}${container.name.suffix}"/>

      <property name="dialect" value="${gatein.jcr.datasource.dialect}"/>

    </properties-param>

  </init-params>

</component>

	`conf-path`: A path to a RepositoryService JCR Configuration.
	`max-backup-files`: The maximum number of backup files. This option lets you specify the number of stored backups. Number of backups can not exceed this value. File which will exceed the limit will replace the oldest file.
	`working-conf`: This is optional. See JCR configuration persister for more details. If there is not a `working-conf`, the persister will be disabled.

The JCR Core implementation contains a persister which stores the repository configuration in the related database using JDBC calls - org.exoplatform.services.jcr.impl.config.JDBCConfigurationPersister. The implementation will create and use table JCR_CONFIG in the provided database. But the developer can implement his own persister for his particular usecase.