1.18.2. Multi-database Configuration

You need to configure each workspace in a repository. You may have each one on different remote servers as far as you need.

First of all configure the data containers in the org.exoplatform.services.naming.InitialContextInitializer service. It's the JNDI context initializer which registers (binds) naming resources (DataSources) for data containers.

For example (standalone mode, two data containers jdbcjcr - local HSQLDB, jdbcjcr1 - remote MySQL):


<component>

    <key>org.exoplatform.services.naming.InitialContextInitializer</key>

    <type>org.exoplatform.services.naming.InitialContextInitializer</type>

    <component-plugins>

      <component-plugin>

        <name>bind.datasource</name>

        <set-method>addPlugin</set-method>

        <type>org.exoplatform.services.naming.BindReferencePlugin</type>

        <init-params>

          <value-param>

            <name>bind-name</name>

            <value>jdbcjcr</value>

          </value-param>

          <value-param>

            <name>class-name</name>

            <value>javax.sql.DataSource</value>

          </value-param>

          <value-param>

            <name>factory</name>

            <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>

          </value-param>

          <properties-param>

            <name>ref-addresses</name>

            <description>ref-addresses</description>

            <property name="driverClassName" value="org.hsqldb.jdbcDriver"/>

            <property name="url" value="jdbc:hsqldb:file:target/temp/data/portal"/>

            <property name="username" value="sa"/>

            <property name="password" value=""/>

          </properties-param>

        </init-params>

      </component-plugin>

      <component-plugin>

        <name>bind.datasource</name>

        <set-method>addPlugin</set-method>

        <type>org.exoplatform.services.naming.BindReferencePlugin</type>

        <init-params>

          <value-param>

            <name>bind-name</name>

            <value>jdbcjcr1</value>

          </value-param>

          <value-param>

            <name>class-name</name>

            <value>javax.sql.DataSource</value>

          </value-param>

          <value-param>

            <name>factory</name>

            <value>org.apache.commons.dbcp.BasicDataSourceFactory</value>

          </value-param>

          <properties-param>

            <name>ref-addresses</name>

            <description>ref-addresses</description>

            <property name="driverClassName" value="com.mysql.jdbc.Driver"/>

            <property name="url" value="jdbc:mysql://exoua.dnsalias.net/jcr"/>

            <property name="username" value="exoadmin"/>

            <property name="password" value="exo12321"/>

            <property name="maxActive" value="50"/>

            <property name="maxIdle" value="5"/>

            <property name="initialSize" value="5"/>

          </properties-param>

        </init-params>

      </component-plugin>

    <component-plugins>

    <init-params>

      <value-param>

        <name>default-context-factory</name>

        <value>org.exoplatform.services.naming.SimpleContextFactory</value>

      </value-param>

    </init-params>

  </component>

We configure the database connection parameters:

driverClassName, e.g. "org.hsqldb.jdbcDriver", "com.mysql.jdbc.Driver", "org.postgresql.Driver"
url, e.g. "jdbc:hsqldb:file:target/temp/data/portal", "jdbc:mysql://exoua.dnsalias.net/jcr"
username, e.g. "sa", "exoadmin"
password, e.g. "", "exo12321"

There can be connection pool configuration parameters (org.apache.commons.dbcp.BasicDataSourceFactory):

maxActive, e.g. 50
maxIdle, e.g. 5
initialSize, e.g. 5
and other according to Apache DBCP configuration

When the data container configuration is done, we can configure the repository service. Each workspace will be configured for its own data container.

For example (two workspaces ws - jdbcjcr, ws1 - jdbcjcr1):


<workspaces>

  <workspace name="ws" auto-init-root-nodetype="nt:unstructured">

    <container class="org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer">

    <properties>

      <property name="source-name" value="jdbcjcr"/>

      <property name="dialect" value="hsqldb"/>

      <property name="multi-db" value="true"/>

      <property name="max-buffer-size" value="200K"/>

      <property name="swap-directory" value="target/temp/swap/ws"/>   

    </properties>

    </container>

    <cache enabled="true">

      <properties>

        <property name="max-size" value="10K"/><!-- 10Kbytes -->

        <property name="live-time" value="30m"/><!-- 30 min -->

      </properties>

    </cache>

    <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex">

    <properties>

      <property name="index-dir" value="target/temp/index"/>

    </properties>

    </query-handler>

    <lock-manager>

    <time-out>15m</time-out><!-- 15 min -->

    <persister class="org.exoplatform.services.jcr.impl.core.lock.FileSystemLockPersister">

      <properties>

      <property name="path" value="target/temp/lock/ws"/>

      </properties>

    </persister>

    </lock-manager>

  </workspace>

  <workspace name="ws1" auto-init-root-nodetype="nt:unstructured">

    <container class="org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer">

    <properties>

      <property name="source-name" value="jdbcjcr1"/>

      <property name="dialect" value="mysql"/>

      <property name="multi-db" value="true"/>

      <property name="max-buffer-size" value="200K"/>

      <property name="swap-directory" value="target/temp/swap/ws1"/>   

    </properties>

    </container>

    <cache enabled="true">

      <properties>

        <property name="max-size" value="10K"/>

        <property name="live-time" value="5m"/>

      </properties>

    </cache>

    <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex">

    <properties>

      <property name="index-dir" value="target/temp/index"/>

    </properties>

    </query-handler>

    <lock-manager>

    <time-out>15m</time-out><!-- 15 min -->

    <persister class="org.exoplatform.services.jcr.impl.core.lock.FileSystemLockPersister">

      <properties>

      <property name="path" value="target/temp/lock/ws1"/>

      </properties>

    </persister>

    </lock-manager>

  </workspace>

</workspaces>

source-name: A javax.sql.DataSource name configured in InitialContextInitializer component (was sourceName prior JCR 1.9);
dialect: A database dialect, one of "hsqldb", "mysql", "mysql-utf8", "pgsql", "oracle", "oracle-oci", "mssql", "sybase", "derby", "db2", "db2v8" or "auto" for dialect autodetection;
multi-db: Enable multi-database container with this parameter (set value "true");
max-buffer-size: A a threshold (in bytes) after which a javax.jcr.Value content will be swapped to a file in a temporary storage. I.e. swap for pending changes.
swap-directory: A path in the file system used to swap the pending changes.

In this way, we have configured two workspace which will be persisted in two different databases (ws in HSQLDB, ws1 in MySQL).

Note

Starting from v.1.9 repository configuration parameters supports human-readable formats of values (e.g. 200K - 200 Kbytes, 30m - 30 minutes etc)