This article covers a Bloomreach Experience Manager version 11. There's an updated version available that covers our most recent release.

Workspace Configuration


The Workspace element in the repository.xml is used as a template for separate workspace configuration files created for each new workspace. Because of this the Workspace element is not interpreted directly from the repository configuration file. Instead the workspace configuration template is first copied into the workspace configuration file which is then interpreted to set up the configured workspace components. Thus modifying the workspace configuration template in the repository configuration file will not affect existing workspace configurations.

An example Jackrabbit workspace configuration can be found in the Jackrabbit documentation. Hippo Repository has a custom workspace configuration for enabling fast faceted navigation through custom indexing. The main differences with a default Jackrabbit workspace configuration are the SearchIndex class and indexingConfigurationClass. See Search Index configuration for explanation of all <SearchIndex> parameters.

The minimal Hippo Repository workspace configuration looks like:

<Workspace name="${}">
  <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
    <param name="path" value="${wsp.home}"/>
  <PersistenceManager class="org.apache.jackrabbit.core.persistence.pool.H2PersistenceManager">
    <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>
    <param name="schemaObjectPrefix" value="${}_"/>
  <SearchIndex class="org.hippoecm.repository.FacetedNavigationEngineImpl">
    <param name="indexingConfiguration" value="indexing_configuration.xml"/>
    <param name="indexingConfigurationClass" value="org.hippoecm.repository.query.lucene.ServicingIndexingConfigurationImpl"/>
Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?