This documentation applies to the 8.0 version of Remedy Action Request System, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

How FTS indexing works

BMC Remedy AR System uses the arserverd process (arserver.exe on Windows) to insert, update, or delete data in the FTS indexes. Threads from the Full Text Indexing queue perform the indexing. This queue has one thread by default, but you can configure more threads as needed. For more information, see the "Defining queues and configuring threads" section in Setting ports and RPC numbers.

The indexing mechanism is based on an offline model, where indexing tasks are recorded in a system table (ft_pending) in the database during the originating transaction. The originating transaction typically involves a create entry, set entry, merge entry, or delete entry operation on a form where a field indexed for full text search exists.

A full text dispatcher thread processes the indexing tasks in real time on a first-in, first-out basis, queuing them for indexing threads to process. As a result of this indexing model, the performance of the originating transaction is affected only marginally by inserting the indexing task record into the system table, and is not subject to delays associated with full text indexing. However, the data might not be immediately available for searching. The size of the delay depends on the size of the indexing queue and the availability of system resources to perform the indexing.


BMC recommends that you perform bulk indexing during off-peak hours, such as during a maintenance window.

If the administrator has disabled indexing, indexing tasks are still recorded, preserving the changes for later inclusion when indexing is enabled.

This section contains information about:

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.