Configuration keys - variable substitution

Configuration keys (search package, data source, results page, server) sometimes include some variables that are expanded dynamically by Funnelback.

These variables are used to prevent the hard-coding of certain values that may change.

It is unlikely you will need to use any of these. The following is presented for reference purposes and the variables are most likely to be observed in older configurations when performing an upgrade, or within system-level configuration which can only be accessed by Funnelback system administrators.

Variables

The following variables can be used within the values of a subset of configuration keys when editing the search package, data source or results page configuration.

When you save a configuration key from the Configuration keys list below, variables will also be inserted if they match a substring in the key’s value. If you save a key with the value /opt/funnelback/conf/common-misspellings.txt.default it will be saved as $SEARCH_HOME/conf/common-misspellings.txt.default.

$COLLECTION_NAME: This is replaced with the data source ID or search package ID for the current data source or search package.
$SEARCH_HOME: This is replaced with the Funnelback installation home path. (usually /opt/funnelback/)
$CURRENT_VIEW: (deprecated) This is used in workflow commands (pre_* and post_* keys) and is replaced with either 'live' or 'offline' depending on the context of the command.
$GROOVY_COMMAND: (deprecated) This is used in workflow commands (pre_* and post_* keys) when executing a Groovy script and is replaced with the system path to Groovy.

Example

filter.jsoup.undesirable_text-source.default-misspellings=$SEARCH_HOME/conf/common-misspellings.txt.default
post_index_command=$SEARCH_HOME/bin/padre-gs $SEARCH_HOME/data/$COLLECTION_NAME/$CURRENT_VIEW/idx/index $SEARCH_HOME/conf/$COLLECTION_NAME/gscopes.cfg