Incomplete or false search results are returned (FTS)

If search results are not appearing as expected in your BOC product, this may be due to an invalid or outdated dataset in the Full-Text Search (FTS) index.

This issue can occur if the automatic clean-up job that removes old files fails, or if the system lacks the necessary read/write permissions for the folder where the FTS index is stored. Typically, this folder is the temporary directory located at: C:\Windows\TEMP

Another possible cause is a reinstallation of your web server (e.g., Apache Tomcat).
If the axw.ids file is not properly transferred during this process, it can negatively affect the search index. If you update your tomcat web service installation, please make sure to follow our guide:  How do I migrate the Tomcat-side configuration of a BOC product?

How do I confirm, something is wrong with my FTS Index?

Problems with the FTS Index can be identified in BOC Product logs.

Here are some examples, how those log entries may look like:

[FATAL] [boc.adoxx.fulltext.JNIIndexWriter] Could not open index (C:\windows\TEMP\FTS_4092DF8C-2BA8-4C08-AC6A-1DDD8DC79353\{30961770-dd4b-4c94-b6a5-f892f8a12f67}-998775608189594953\{ab71db7b-a17a-4d10-be36-f33eb745f153}) org.apache.lucene.index.CorruptIndexException: Unexpected file read error while reading index. 
2023-11-24 08:36:38.142 [10484] [WARN] [Index Updater] Error during index update, returned code UnexpectedError 
2023-11-24 08:36:38.126 [10484] [ERROR] [C++Assert] expr: !pDocBuf->IndexClosed() code: NS_ERROR_FAILURE (0x80004005) file: ..\src\applications\fts\index\afts_index_updater.cxx line: 1179 

On how to read your own logs, please consult our Log Guide.

Solution: Manually rebuilding FTS Index via webclient

This guide applies to ADONIS 16, ADOIT 17, and ADOGRC and later versions. For instructions applicable to earlier versions, please click here.

Important: Be aware that this option puts a high load on server ressources and will impact performance on the deployment itself. It is strongly recommended to perform this task in off-peak hours.

1.) Log into your Administration View with an Admin User and click on More options (1). 

 

2.) Choose the Option Server (2)

3.) Choose the option Re-initialise search index (3) and confirm your entry in the subsequent popup.

 

Manually rebuilding FTS Index via webclient (below ADONIS 16, ADOIT 17 and ADOGRC 13)

1.) Open the web client in your internet-browser of choice and log into your admin view with a suitable admin user. For details how to reach your admin.view please see Admin Page. The described path is the same for all BOC Products. 

2.) When logged in, click the 3 dots in the upper left corner and click the option Server

2.) Choose the option Re-initialise search index and confirm your entry in the subsequent popup.

Important: Be aware that this option puts a high load on server ressources and will impact performance on the deployment itself. It is strongly recommended to perform this task in off-peak hours.

Additional Information (on premise only)

Another option to rebuild the FTS index is to relocate the folder the index is writing in, especially if the access for the current location is restricted.

This can be achieved by editing [PRODUCT]/conf/adoxx.conf with an editor of your choice.

In the following example, the FTS Index is moved inside the BOC-Product's installation path by removing the hash-symbol before ADOXX_INDEXES_DIRand replacing %temp% with /_FTS

If it is desired to move the FTS Index to a different location, the full path is needed. A full restart needs to be done afterwards.