Redirecting full-text indexing
Redirect full-text indexing when configuring a back-end server, or when the local machine does not have full-text indexing (FTI). This can be done on any server if FTI is handled on a different server, for back-end servers when configuring asynchronous load balancing, or when configuring network load balancing.
Before you begin
To redirect full-text indexing, ensure that in the file server.App\Utilities\SolrLucene\bin\solr.in.cmd, the environment variable SOLR_JETTY_HOST, which sets the network interface the Solr binds to, has a value that properly reflects the narrowest possible network interface access. To prevent administrators from accidentally exposing Solr more widely than intended, this value defaults to 127.0.0.1. Administrators should think carefully about their deployment environment and set this value as narrowly as required before going to production. In environments where security is not a concern, 0.0.0.0 can be used: it allows Solr to accept connections on all network interfaces.
About this task
The configuration for full-text indexing is handled by the Crawler and SolrLucene entries in the registry.
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Trisoft\TriDK\TridkApp\InfoShareAuthor]
"CrawlerIndexEngineType"="ApacheSolrLucene"
"SolrLuceneBaseUrl"="https://localhost:8080/solr"
"SolrLuceneHTTPTimeout"="180"
"SolrLuceneHTTPRetries"="5"
To redirect full-text indexing on any server to the server holding the full-text indexing role: