Retain Indexing

The indexing engine can be changed between the two engines, but requires the index to be re-created. Recreating the indexes is a time consuming process and should not be done unless required. Searches of the Retain Archive during the index re-creation or migration process may not contain all results.

First reading that should be done should be from the RetainServer UI itself under the Indexing Engine section.

Level 1

Indexing Engine

This is where you set the indexing engine Retain will use to index message metadata, message content, and message attachments. Lucene is the most widely used by far, so the screen defaults to Lucene.

Lucene

Lucene is hosted locally on the same machine as the Retain Server, and requires no further configuration, but does not have the same options or the extent of the capabilities as the Exalead engine does, but is sufficient for most customers' needs and we recommend using this indexer. It is quickly catching up to Exalead in capabilities.

Exalead

Because Exalead is a much more robust indexing engine it requires its own server and resources. As such, when Exalead is selected as the indexing engine, a connection address and starting base port are required. The default BASEPORT is 10000. To ensure that the connection to the Exalead server is working, the ‘Test Connection’ button may be selected, which triggers Retain to contact the Exalead server. The results should shortly appear as a small notification window in your browser.