Since kernel 2.0.7 and 2.1, it is possible to use system properties in literal values of component configuration meta data. This makes it possible to resolve properties at runtime instead of providing a value at packaging time.

See below an example of a configuration file based on system properties:

  <component>

    <key>org.exoplatform.services.database.HibernateService</key>

    <jmx-name>database:type=HibernateService</jmx-name>

    <type>org.exoplatform.services.database.impl.HibernateServiceImpl</type>

    <init-params>

      <properties-param>

        <name>hibernate.properties</name>

        <description>Default Hibernate Service</description>

...

        <property name="hibernate.connection.url" value="${connectionUrl}"/>

        <property name="hibernate.connection.driver_class" value="${driverClass}"/>

        <property name="hibernate.connection.username" value="${username}"/>

        <property name="hibernate.connection.password" value="${password}"/>

        <property name="hibernate.dialect" value="${dialect}"/>

...

      </properties-param>

    </init-params>

  </component>

As these are system properties you use the -D command: java -DconnectionUrl=jdbc:hsqldb:file:../temp/data/exodb -DdriverClass=org.hsqldb.jdbcDriver Or better use the parameters of eXo.bat / eXo.sh when you start eXo Portal: set EXO_OPTS="-DconnectionUrl=jdbc:hsqldb:file:../temp/data/exodb -DdriverClass=org.hsqldb.jdbcDriver"