1. Runtime Administration Guide
  2. Building Text Search Indexes

Building Text Search Indexes

The three types of builds you can perform are:

  • Full

  • Incremental

  • Clear

Full

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.

Incremental

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.

See "Understanding Text Search Controls" in the JD Edwards EnterpriseOne Tools Form Design Aid Guide

Clear

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 will need to do a full build. 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 on the Report and Row menus.

The Full Build and clear build can be called either interactively (via Row->Build) or as a batch (via Report->Build).

The build can also be scheduled using the JD Edwards EnterpriseOne Scheduler by running the following UBEs:

  • R958001A - XJDE0001 (SES Text Search Build).

  • R958001A - XJDE0003 (SES clear build).

Note: Using interactive applications to run the full build is not recommended for views having a large number of records. This is because JDENETTimeout of the FAT/Enterprise server and the EnterpriseServerTimeout of the HTML server have to be increased so that requests sent to Enterprise Server or the requests sent to Text Search Kernel from Call Object kernel will not timeout.The numbers to which these settings have to be increased vary from view to view and changing these settings will have an impact on other functionality as well.When building views with a large number of records, it is recommended to use the Report R958001A (i.e. by creating version for the desired view).