File system paths

eXo Platform requires the read/write access to several paths in the local file system.

# Arjuna configuration
com.arjuna.ats.arjuna.objectstore.objectStoreDir=${gatein.data.dir}/jta
.....

# Directory for common data (in cluster, mount it as a network shared directory between nodes)
# On standalone JBoss app server it is assignet to ${jboss.server.data.dir} by default.
exo.shared.dir=../gatein

# Configuration directory (in cluster, this directory is per node)
# Usual locations of configuration directory:
# for Tomcat app server it is ${catalina.home}/gatein/conf.
# for JBoss app server it is ${jboss.server.home.dir}/conf/gatein.
gatein.conf.dir=${catalina.home}/${exo.conf.dir.name}

# Data directory
gatein.data.dir=${exo.shared.dir}/data

# path for any JCR data 
gatein.jcr.data.dir=${gatein.data.dir}/jcr

# path for file data inserted in JCR
gatein.jcr.storage.data.dir=${gatein.jcr.data.dir}/values

# path for the jcr index
gatein.jcr.index.data.dir=${gatein.jcr.data.dir}/index

The following table explains what goes in which path. The Temporary column indicates if the data are temporary or persistent (V: temporary, X: persistent).

Variable	Content	Temporary
`com.arjuna.ats.arjuna.objectstore.objectStoreDir`	JTA transactional data.	V
`gatein.jcr.data.dir`	Directory for JCR data.	X
`gatein.jcr.data.dir`/swap	Directory for swapped data of JCR	V
`gatein.jcr.storage.data.dir`	Binary value storage for JCR.	X
`gatein.jcr.index.data.dir`	Lucene index for JCR.	X

Each variable can be defined as an absolute or a relative path. The default configuration combines them to obtain a compact tree:

/gatein       # gatein.data.dir
  /data
    /hsql
    /jcr      # gatein.jcr.data.dir
      /index  # gatein.jcr.index.data.dir    
      /swap
      /values # gatein.jcr.storage.data.dir    
    /jta