Because JCR Configuration is a very advanced topic, it is recommended you:
Learn about eXo JCR configuration.
Use default values, change them only if you know what you are doing.
Understand how to configure datasource in the Database chapter.
The configurations introduced here are a subset of JCR configurations. There are many JCR configurations which are packed in .war files, so you have to unpack to edit them. To avoid unpacking them, the subset is externalized to be configured easily in $PLATFORM_TOMCAT_HOME/gatein/conf/configuration.properties (in Tomcat) or $PLATFORM_JBOSS_HOME/standalone/configuration/gatein/configuration.properties (in JBoss). Here is the list of externalized configurations with their short descriptions.
Repository:
gatein.jcr.repository.default=repository gatein.jcr.workspace.default=collaboration gatein.jcr.workspace.system=system
In which, "repository", "collaboration" and "system" are names of default repository, default workspace and system workspace respectively. Refer to Repository for details.
Datasource:
gatein.jcr.datasource.name=java:/comp/env/exo-jcr gatein.jcr.datasource.dialect=auto gatein.jcr.db-structure-type=single
These configurations are applied to all workspaces. Refer to Workspace for details.
Jgroups:
gatein.jcr.jgroups.config=file:${gatein.jgroups.config}This externalizes the jgroups-configuration parameter of all workspace caches, query-handlers and lock-managers. Refer to Workspace for details.
Value Storage:
gatein.jcr.storage.enabled=true
This externalizes the enabled property of file system value-storage (that is configured at workspace level). The true value means all binary values are stored in file system. The false value means all binary values are stored in the database. Refer to Value Storage plugin for data container for details.
See also