Versions Compared

Version Old Version 1 New Version 2
Changes made by

Anonymous

Magnus Frank

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You have to setup the following DAM Center configuration parameters. They can be found in System tools → DigizuiteTM Configuration:

...

Required configuration parameters

In order for Solr to work, the following parameters are needed:

  • Solr URL (default: http://localhost:8983/solr 
  • SOLR_UNC – the UNC path to Solr (specifically the SOLR_SERVICE_DIR from above); e.g. \\solr.dmz.digieyez.dk\c$\Solr\SolrService 
  • SOLR_UNC_USERNAME – the account used to access SOLR_UNC. If left blank, the assetstream user will be used.
  • SOLR_UNC_PASSWORD – the password used to access SOLR_UNC. If left blank, the assetstream password will be used.
  • SOLR_UNC_DOMAIN – the domain used with SOLR_UNC_USERNAME. If left blank, the assetstream domain will be used.)
  • Solr UNC (default: C:\Bitnami\solr-8.3.1-1\apache-solr\server\solr)

The goes into the Digizuite web.config in the Appsettings section.


Optional configuration parameters

Once Solr is up and running, there are some optional configuration parameters that can be used to tune performance and searching capabilities.

The first set of configuration parameters are found in the Digizuite configuration area (System tools/Digizuite Configuration. These are two constants that may be changed:

NameDescriptionDefault value
SEARCHPROXY_DEBOUNCE_STRATEGY

This parameters is used to determine which debounce strategy to use when updating the index.

The options are:

  • DEBOUNCE
  • THROTTLING

The first one debounces the events that update the index for X seconds and if another event arrives 
for the specific ID, then the debouncer interval X is restarted. This means the index is only updated
once when the system settles for the specific ID.

The latter one is a throttling strategy, where all events are delayed for X seconds. 

Info

The recommendation is to use the DEBOUNCE strategy


DEBOUNCE
SEARCHPROXY_DEBOUNCE_TIME

This parameter is used to determine the time an event is debounced/throttled. 

This specifies the X seconds mentioned the above describtion for SEARCHPROXY_DEBOUNCE_STRATEGY.

The recommendation here varies on the environment. There are the following recommendations:

  • If the environment is in a migration phase (i.e. a lot of data is updated), this should have a higher value
  • The better the environment, the lower a value you want.

The idea is to keep this is low as possible, without spamming the system. If a lot of data is being updated 
on the same asset, many events are spawned. Each event potentially updates the index. The idea is to 
debounce the events just enough, to collect all updates into one index update.

5


Lastly, we have the option to change the behavior of how Solr interprets indexes and queries. This is done using the concept of Tokenizers

The idea of a Tokenizers is to break a