You are here

Search Services directory structure

After you've installed Alfresco Search Services, several directories and configuration files related to Solr will be available in the Search Services home directory.
The Alfresco Search Services distribution (alfresco-search-services-1.2.x.zip) contains the following artifacts:
  • solrhome directory: This is the Solr configuration directory that is specific to Alfresco. It contains the following sub-folders and files:
    Folder/File Description
    alfrescoModels When you install Search Services, it creates an empty alfrescoModels directory. When Solr first talks to Alfresco, it pulls the model definitions into this directory.
    conf This directory contains the shared.properties file. See Search Services externalized configuration.
    templates This directory contains the core templates that define the base configuration for a new Solr core with some configuration properties. This directory also contains the /rerank/conf/solrcore.properties file.
    solr.xml This file defines the Solr web application context.
  • logs directory: This directory contains the Solr-specific logging configuration file.
    Folder/File Description
    log4j.properties This is the configuration file for Solr-specific logging. The Solr log file can be found at <SOLR_HOME>/logs/solr.log.
  • solr directory: This directory contains the Solr binaries and runtime Java library files.
  • contentstore directory: This directory does not appear in the alfresco-search-services-1.2.x.zip file. It is automatically created after your Solr cores are created and they start indexing. It stores the cache of all the content.
  • solr.in.cmd: Use this file to specify additional Solr configuration options for Windows.
  • solr.in.sh: Use this file to specify additional Solr configuration options for non-Windows platforms, such as Linux and Mac OS X.
  • README.MD: This file provides version information for Alfresco Content Services, Alfresco Search Services, and Solr.

Sending feedback to the Alfresco documentation team

You don't appear to have JavaScript enabled in your browser. With JavaScript enabled, you can provide feedback to us using our simple form. Here are some instructions on how to enable JavaScript in your web browser.