Workspace Configuration

Overview

The Workspace element in repository.xml serves as a template for workspace configuration files. When a new workspace is created, the system copies this template to generate the workspace's configuration file. The repository does not interpret the Workspace element directly from repository.xml. Instead, it reads the copied workspace configuration file to initialize workspace components.

Modifying the workspace configuration template in repository.xml does not update existing workspace configurations. Changes only apply to new workspaces created after the modification.

Workspace Configuration Details

Jackrabbit provides a standard workspace configuration example in its documentation. Bloomreach Content (Hippo Repository) uses a custom workspace configuration to support fast faceted navigation through specialized indexing. The primary differences from the default Jackrabbit configuration are the custom SearchIndex class and the indexingConfigurationClass parameter.

For details on all <SearchIndex> parameters, see Search Index configuration.

Minimal Workspace Configuration Example

The following example shows a minimal workspace configuration for Hippo Repository:

<Workspace name="${wsp.name}">
  <FileSystem class="org.apache.jackrabbit.core.fs.local.LocalFileSystem">
    <param name="path" value="${wsp.home}"/>
  </FileSystem>
  <PersistenceManager class="org.apache.jackrabbit.core.persistence.pool.H2PersistenceManager">
    <param name="url" value="jdbc:derby:${wsp.home}/db;create=true"/>
    <param name="schemaObjectPrefix" value="${wsp.name}_"/>
  </PersistenceManager>
  <SearchIndex class="org.hippoecm.repository.FacetedNavigationEngineImpl">
    <param name="indexingConfiguration" value="indexing_configuration.xml"/>
    <param name="indexingConfigurationClass" value="org.hippoecm.repository.query.lucene.ServicingIndexingConfigurationImpl"/>
  </SearchIndex>
</Workspace>
copy