|
|
|
The seeker.config file defines all the application settings for the indexing applications
Key |
Required |
Default |
seekerIndexer.databaseType |
Yes |
mssql |
seekerIndexer.databaseConnectionString |
Yes |
Data Source=server; Initial Catalog=clarify; User Id=user; Password=password; |
seekerCommon.fileSystemIndexDirectory |
Yes |
[Installation Path]\seekerIndex |
seekerCommon.documentSpecificationsFilePath |
Yes |
[Installation Path]\config\documentSpecifications.xml |
seekerIndexer.dovetailDocumentPollingFrequencyInSeconds |
Yes |
15 |
seekerIndexer.fileDocumentPollingFrequencyInSeconds |
Yes |
120 |
seekerIndexer.maxUpdatesPerMessageInDovetailDocumentMessage |
No |
100 |
seekerIndexer.maxUpdatesPerMessageInFileDocumentMessage |
No |
25 |
seekerIndexer.fileDocumentValidationPollingFrequencyInHours |
Yes |
3 |
seekerIndexer.documentSummaryFieldLength |
No |
1000 |
seekerIndexer.numberOfIndexChangesBeforeOptimization |
No |
1000 |
seekerIndexer.numberOfIndexSegmentsAfterOptimization |
No |
3 |
Database settings
If you skipped the database settings section during the install, you must edit a configuration file which tells Seeker how to talk to the Dovetail CRM database. Optionally, you can control where index files are created and how often the Seeker Service updates your index.
Important: We advise that you limit the database credentials used for running indexing applications to be read-only.
Where Is The Seeker Index Located?
Optionally, you can change the location of the seekerCommon.fileSystemIndexDirectory to control where the search index will be created. Be aware that the Seeker web application will need to have at least read access to this path.
What is Indexed Out of the Box?
Dovetail Seeker is shipped with a predefined set of specifications about what Dovetail CRM entities to index. These specifications are defined in an XML configuration file.
You can use the seekerCommon.documentSpecificationsFilePath in the configuration file to control the location where indexing applications look for document specifications. This should be an absolute path.
How Often Should the Seeker Service Update Dovetail Specifications?
The Seeker Service by default checks to see if the search index needs updating Dovetail CRM entities every 15 seconds and file documents every 120 seconds (2 minutes). You can change the value of the seekerIndexer.dovetailDocumentPollingFrequencyInSeconds entry to be the number of seconds you want Seeker Service to wait between index updates for Dovetail CRM entities and seekerIndexer.fileDocumentPollingFrequencyInSeconds for file documents.
How Many Documents Get Updated Per Message?
The Dovetail Seeker Service automatically batches up the number of document updates per Dovetail CRM message to 100 and file document message to 25. You can change the value of seekerIndexer.maxUpdatesPerMessageInDovetailDocumentMessage entry for Dovetail CRM entities and seekerIndexer.maxUpdatesPerMessageInFileDocumentMessage for file documents. If either entry is left blank, the service will not batch updates and do them all at once.
How Often Should Invalid File Documents Get Removed?
The Dovetail Seeker service automatically removes file documents from the index that have moved or been deleted. The default time for removing the invalid files from the index is 3 hours. You can change the value of seekerIndexer.fileDocumentValidationPollingFrequencyInHours entry.
How Many Characters Should Be Included In Every Document's Summary Field?
To avoid bloating the index with extremely large document summaries it is recommended to limit the number of characters included from the file being indexing in the summary field of the document. You can change the value of seekerIndexer.documentSummaryFieldLength to control the number of characters included in the file document's summary field.
After How Many Document Updates Should The Index Optimized?
By default the Seeker Service will only optimize the search index after 10000 documents have been added or updated in the search index. You can change the value of seekerIndexer.numberOfIndexChangesBeforeOptimization entry to be a numeric value representing the number of documents that need to be changed before the index will be updated.
How Many Index Segments Should The Index Be Optimized To?
When the index is optimized Lucene works to reduce the number of index segments. For ideal search performance the number of index segments is one. This setting seekerIndexer.numberOfIndexSegmentsAfterOptimization defaults to 3 segments in an attempt to strike a balance between search performance and index optimization time. If you experience long index optimization times you should increase this value. If you would like to boost your search performance reduce this value to 1.
See Also |
Next |