Indexing with Back4

Build 1501 on 14/Nov/2017  This topic last edited on: 25/Aug/2014, at 12:08

Since version 1.3.1181.0 any Tark4/GN4 installation having full-text searches configured must have a Back4 configured and running.

This because the indexing process has been moved into Back4 application which will have many benefits like performance improvements.

This means that Back4 will take care of index/unindex Tark4/GN4 stuff and keep the indexes in sync.

Every time an object is created, edited or deleted it is added to an index queue table. Back4 will scan that table (interval is defined with commitEvery attribute) and will sync the indexes with the changes cleaning the table once the operation is completed.

Related Back4 configuration attributes:

commitEnabled:  enable indexing process. in multiple Back4 environment only in 1 instance should be enabled.

commitEvery: Exalead commit interval, default every minute.

commitPriority: commit task priority.

Example:

<Back4Config xmlns="http://www.teradp.com/schemas/GN4/1/Back4Config.xsd" 
 PollingInterval="20000" 
              TaskDuration="20000"
             NProcThreads="4" 
             SynchTimeOut="00:05:00" 
             WebUrlPrefix="http://*:7373/" 
             LogMaxTime="168" 
             MaxCachedLogins="100" 
             NProcThreadsHighPriority="0" 
             NMinTaskPriorityForHighPriorityThread="5"
             commitEnabled="true"
             commitEvery="00:01:00"
             commitPriority="0">

             ...

A schema and database update is required.

Also BasePortalConfig.xml and BaseStrings.en.xml need to be reimported.