Each mentioned components uses instances of JBoss Cache product for caching in clustered environment. So every element has its own transport and has to be configured in a proper way. As usual, workspaces have similar configuration but with different cluster-names and may-be some other parameters. The simplest way to configure them is to define their own configuration files for each component in each workspace:

<property name="jbosscache-configuration" value="conf/standalone/test-jbosscache-lock-db1-ws1.xml" />

But if there are few workspaces, configuring them in such a way can be painful and hard-manageable. eXo JCR offers a template-based configuration for JBoss Cache instances. You can have one template for Lock Manager, one for Indexer and one for data container and use them in all the workspaces, defining the map of substitution parameters in a main configuration file. Just simply define ${jbosscache-<parameter name>} inside xml-template and list correct value in JCR configuration file just below "jbosscache-configuration", as shown:

Template:

...

<clustering mode="replication" clusterName="${jbosscache-cluster-name}">

  <stateRetrieval timeout="20000" fetchInMemoryState="false" />

...

and JCR configuration file:

...

<property name="jbosscache-configuration" value="jar:/conf/portal/jbosscache-lock.xml" />

<property name="jbosscache-cluster-name" value="JCR-cluster-locks-db1-ws" />

...