JCR data is stored in both SQL databases and File System. JCR Database configuration is explained in Database. The JCR File System configuration is explained in this section.
Typically, the JCR File System data consists of four folders:
JCR indexes.
JCR values storage.
To store JCR value, SQL database is used as primary storage and another directory can be used as a secondary, dedicated storage for BLOB data. It is optional and you can configure to not store BLOB data in File System, by changing the default configuration in the following files. See Configuration overview for how-to.
$PLATFORM_TOMCAT_HOME/gatein/conf/exo.properties (Tomcat).
$PLATFORM_JBOSS_HOME/standalone/configuration/gatein/exo.properties (JBoss).
exo.jcr.storage.enabled=true
JTA (Transaction information).
Swap data (temporary memory space).
By default, these four folders are located under a common directory that is
$PLATFORM_TOMCAT_HOME/gatein/data (Tomcat) or $PLATFORM_JBOSS_HOME/standalone/data/gatein (JBoss).
In production, it is recommended to configure it to use a directory separated from the package. Especially in cluster mode, it should be a network shared folder.
Configuration in Platform Tomcat
In Tomcat, the directory is configured by the environment variable EXO_DATA_DIR.
Edit the bin/setenv-customize.(sh|bat) script:
EXO_DATA_DIR=/mnt/nfs/shared/exo/data
You need to create the script file by copying/renaming the sample bin/setenv-customize.sample.(sh|bat).
See Customizing environment variables for more information.
Configuration in Platform JBoss
In JBoss, the directory is configured by the system property exo.data.dir.
Edit standalone/configuration/standalone-exo.xml like below:
<system-properties>
...
<property name="exo.data.dir" value="/mnt/nfs/shared/exo/data"/>
...
</system-properties>
Note that if you are configuring the cluster mode, the configuration might be different. The file should be
standalone-exo-cluster.xml and the property should be exo.shared.dir.
See Setting up eXo Platform cluster.
See also