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.

A default configuration is installed that connects to the localhost. For example:
[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:

Procedure

  1. On the server, alter SolrLuceneBaseUrl to the URL for SolrLucene on the full-text indexing (FTI) server.
    For example, where fti.example.com is the FTI server's URL for SolrLucene, modify the server's registry with this URL and the correct port, so that it reads:
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Trisoft\TriDK\TridkApp\InfoShareAuthor] 
    "SolrLuceneBaseUrl"="https://fti.example.com:8078/solr"
    full-text indexing is now directed to the server as specified in the registry for SolrLuceneBaseUrl.
  2. Reboot the server or, at minimum, a recycle is required for the application pool.
  3. Disable the crawler service on the server that has been redirected to the FTI server:
    • Click Control Panel > Administrative Tools > Services
    • Double-click on the service named, Trisoft InfoShare Crawler One.

      There may be more than one service. If so, follow the procedure for each.

    • Under the General tab, set the Startup type to Disabled.
  4. To allow incoming requests on the server holding the full-text index role from other servers, add all the servers IPs, or server IP range to the solr.in.cmd
    REM Restrict access to solr by IP address.
    REM Specify a comma-separated list of addresses or networks, for example:
    REM   127.0.0.1, 192.168.0.0/24, [::1], [2000:123:4:5::]/64
  5. Make sure that the Firewall on the machine hosting the full-text index role allows incoming connections on the specified IPs and/or ports.
  6. Restart the TrisoftSolrLucene Windows service on the server holding the full-text index role.