Registry Keys used to Configure the Crawler for all Databases
The Contenta Server installer will add the following registry keys, which are used to support the search engine You will be prompted for most registry settings when you run the Contenta Server installer.
Later, if you decide to change any settings, you can edit the registry for your system (see Configuration Settings).
Registry Settings used for Search Indexing
| Key | Function |
|---|---|
| CONTENTA_SERVER_NAME | The host name of the system on which the Contenta portal server is running. The Contenta App Server installer prompts you to specify the server name. |
| CONTENTA_SERVER_SOCKET | The Contenta portal socket number. The Contenta App Server installer prompts you to specify the server socket number. |
| MAX_WALKER_THREADS | The maximum number of walker threads to launch. The Contenta App Server installer sets this value to 10. |
| MAX_INDEXER_THREADS | The maximum number of index threads to launch. The Contenta App Server installer sets this value to 10. |
| DATABASES_TO_INDEX | The Crawler will connect to the databases specified in this registry entry, and if the databases are configured for indexing, the Crawler will index them (see MARK_DB_FOR_INDEX in Figure 1: Global AppData Settings in Adding a New AppData Key). If you specify more than one database name, separate them with commas. If you are on Oracle, each database must not have an SID specified as part of its name. For example: use Each of the listed databases will be indexed to only one Solr collection, which is used exclusively for that database. For each database, the collection name and URL are configured in AppData (see IDPATH and URL in Figure 1: Global AppData Settings in Adding a New AppData Key). The Contenta App Server installer prompts you to specify the database names to index. Use a comma to separate multiple database names. |
| REREAD_APPDATA_IN_MINUTES | The time, in minutes, before AppData settings will be re-read by the Crawler. The Contenta Application Server installer sets this value to 1 minute. If your database contains a large number of configurations, increasing this setting to a value such as 60 (minutes) or greater may improve Crawler indexing performance. |
| THREADS_DELAY_IN_SECONDS | The time the Crawler sleeps when the maximum number of threads is spawned. After sleeping, the Crawler spawns more threads if the number of threads running is less than maximum number of threads (see MAX_WALKER_THREADS and MAX_INDEXER_THREADS). The Contenta App Server installer sets this value to 3 seconds. |
| SID_TO_INDEX | The SID (Oracle) or DNS (Windows Server) to use for databases listed in DATABASES_TO_INDEX (see DATABASES_TO_INDEX in Figure 1: Global AppData Settings in Adding a New AppData Key).
The Contenta App Server installer prompts you to specify the Oracle SID or Windows Server DNS name. You can configure multiple Crawlers to index databases in the same databases instance (usually a SID points to a database instance). However, it is important that each Crawler index a unique set of databases. Do not configure two Crawlers to index the same database. Each Crawler must run on its own computer. The Crawler can be installed by itself on a computer, it does not require Contenta Server (portal) or Solr. See Step 11 “Installing Contenta Server and Third-Party Components” in the Installing SDL Contenta Server on Windows publication. |
| SOLR_RESPONSE_TIMEOUT_IN_ SECONDS | The time that the Crawler waits for a response from the Solr server after writing data for indexing. The Contenta App Server installer sets this value to 120 seconds. |
| TEMP | The path to the temporary directory used by the Crawler. The Crawler uses an API call that returns the First, it attempts to read Second, if the first attempt fails, it attempts to read Third, if all else fails, it attempts to read |
SOLR_COMMITWITHIN_IN _SECONDS | The Installer creates this value and sets it to 5 seconds. You can enter your own value for this field. This value determines the number of seconds that will lapse before Solr commits changes posted by the Crawler.
For example, if you change the value to 60, changes made to objects in Contenta will not be found in the Solr index for at least one minute. Increasing this value should decrease the likelihood of this indexing error:
However, the default setting is expected to work in all situations. Also, increasing this value could decrease the workload for Solr, as commits will occur with less frequency. |