Keeping Solr Data Current

Xinet is programmed to update the Solr index on a regular basis to capture changes made to assets stored in the database. As an Administrator, you can force the Solr engine to index at faster intervals.

The dblogd.conf file uses the following variables to specify the update process.

•	SolrUpdateMin: Default 10 Seconds

•	SolrUpdateMax: Default 1 Minute

•	SolrEventThresh: Default 25 Events

Events are file modifications events as posted to the webdblog file (the event processed by the dblogd.conf). Metadata changes are tagged as 1 event point, file creation, rename, copy, and make directory events are tagged as 1 event point unless they come from the Portal File Manager where they are tagged as 5 event points. Uploads are tagged as 25 event points, so the uploaded files are displayed as soon as possible.

An Event Threshold causes the Solr update to happen before the Maximum interval has passed, if the number of events is greater than SolrEventThresh, during the time between the Minimum and Maximum.

The default behavior for Solr indexing is to wait a minimum of 10 seconds and a maximum of one minute to complete the update. To keep the Solr index more current, you can update the time interval variables in the Option section of the dblogd.conf file.

CAUTION: Reducing the time values for Solr indexing may affect the performance of Xinet if you have a large database.

To update Solr indexing variables:

1.	In the Administration view, click Database > Admin > Settings.

1.	In the Database Daemon section, click Stop Daemon.

2.	Open dblogd.conf.

Windows: c:/Program Files (x86)/Xinet/WebNative/Admin/dblogd.conf

Unix: /var/adm/webnative/dblogd.conf

3.	Create an [Options] section in the dblogd.conf file.

4.	Add the Solr variables. The following is an extreme example.

• SolrUpdateMin=5

• SolrUpdateMax=10

• SolrEventThresh=10

5.	Save your updates.

6.	In the Administration view, click Database > Admin > Settings Database Daemon section, click Start Daemon.

For more information about DB daemons, see About the database daemons.

Setting your own Schedule to Purge Deleted Files From your Solr Database

Administrators can removed index entries of deleted files from their Solr Database to improve the performance of Quick Search and browsing. Setting a schedule to clear deleted files from the Solr Database index is done by setting your own solrutil -purgedeleted schedule in the dblogd.config file. Without this setting, the purge is scheduled to happen Mondays at midnight.

Important: Schedule your Solr Database purge process to remove unwanted index entries of deleted files before scheduling a backup or periodic sync and table checks to avoid CPU performance issues. For more information, see Setting your own Schedule to Purge Deleted Files From your Solr Database.

Tip:	Administrators specify the location of the Solr Database in the Administration view - Database > Admin > Searching tab.

Note: Don’t get confused about the -purgedeleted option. As mentioned above, solrutil -purgedeleted option applies to purging deleted files in the Solr Database. The option dbmgr -purgedeleted purges the Xinet database (Venture). In addition, when you run the solrutil -purgedelete option, it runs independently from other processes (for example, dblogd).

To set a schedule to purge deleted file entries from your Solr Database:

1.	Open the dblogd.config file.

Windows: c:/Program Files (x86)/Xinet/WebNative/Admin/dblogd.conf

Unix: /var/adm/webnative/dblogd.conf

2.	Add a Solr Purge section to this file. For example:

[Solr Purge]

Day=Sun

Hour=1

Minute=0

Second=0

Count=1

3.	Save the dblogd.conf file.