Building Text Search Indexes

There are four types of builds you can perform:

• Full

• Incremental

• Optimize

• Clear

A full build indexes all the data referenced by a business view and creates a new text search index or replaces an existing text search index. You should schedule full builds regularly, depending on the frequency with which the data changes.

Note: If a user adds a new media object to a specific record in a business view and as a result, exceeds the media object limit defined in the previous full build, the change will only take affect after the next full build is complete. In other words, the incremental build will not add this change in the text search index for this business view.

Some applications automatically perform incremental builds. An incremental build takes data entered since the last full build and adds it to the end of the text search index. This makes the data available for searching, but each time an incremental build runs, it decreases the efficiency of the text search index. To optimize the efficiency of the text search index, you need to run an optimize build.

An optimize build takes the data entered since the last full build and re-indexes it. This increases text search efficiency and ensures that text searches cover recently added data. An optimize build is not as resource-intensive as a full build, so you can schedule it more frequently.

A clear build removes all data from the text search index. Under normal circumstances you would not clear a text search index, except to free file system storage. Before you can search again, you need to do a full build. However, if you do a search after a clear build, there is no data in the index to return.

You can perform builds manually or schedule them to occur automatically. The manual Build options are off the Report and Row menus. Schedule builds using the JD Edwards EnterpriseOne Scheduler by running the following UBEs:

• R958001 - XJE001 (Full Build).

• R958001 - XJDE002 (Optimize).

• R958001 - XJDE003 (Clear).