When to run the free-text batch load command

Generally, PolicyCenter updates the Guidewire Solr Extension whenever someone changes a policy and that change affects index documents stored there. In response, the Guidewire Solr Extension incrementally indexes the changed information. Occasionally, you need to load the Guidewire Solr Extension and have it build new indexes based on the newly loaded information.

Important: Users must not perform free-text searches while the free-text batch load command runs. Otherwise, the search results will be incomplete. Set the EnableDisplayBasicSearchTab script parameter to false to temporarily hide the free-text search user interface.

Run the free-text batch load command whenever any of the following occur:

Policies are bulk loaded into the PolicyCenter application database.
Indexes become corrupted in the Guidewire Solr Extension, as reported by the Guidewire Solr Extension web application.
Changes are made to the metadata definitions of entities and relationships in the policy graph, and these changes affect index documents stored in the Guidewire Solr Extension.
Changes are made to attribute definitions in schema.xml.
Changes to the mapping (policy-search-config.xml or custom mappers) that affect already indexed periods.
Your instance of PolicyCenter is upgraded to a later version, and the upgrade changes metadata definitions for index documents stored in the Guidewire Solr Extension.

Do not run the free-text batch load command if you configured free-text search for embedded operation. Whenever the Guidewire Solr Extension runs in embedded mode, use the Internal Tools Free Text Search screen to execute the batch load command instead. If you run the batch load command with embedded operation, PolicyCenter limits the number of index items to 10,000.