To update the Apache Solr index, complete the following steps:
- On the SAS middle tier machine, stop the SASServer8_1 Web AppServer instance by executing the following command:
<sas_config>/Lev1/Web/WebAppServer/SASServer8_1/bin/./tcruntime-ctl.sh stop
- Remove the Apache Solr core by executing the following command:
<solr-home>/bin/./solr delete -c rgf -p 8983
- Stop the Apache Solr services by executing the following command:
<solr-home>/bin/./solr stop -p 8983
- Create the Apache Solr rgf core by executing the following command
<solr-home>/bin/./solr create -c rgf -p 8983
- Back up the following files in the <solr-home>/server/solr/rgf/conf directory:
managed-schema
solrconfig.xml
configoverlay.json
- Back up the following file in the <solr-home>/server/resources directory:
log4j.xml
Note: Older Apache Solr releases contain the log4j.properties file
- On the SAS middle tier machine, navigate to the <SASHome>/SASRiskGovernanceFrameworkMidTier/7.4/Config/Samples/Solr<version> directory and perform the following tasks:
- Copy the managed-schema,solrconfig.xml and configoverlay.json files from above directory to the <solr-home>/server/solr/rgf/conf directory. This action overwrites existing files.
- Copy the log4j.properties file from above directory to the <solr-home>/server/resources directory. This action overwrites existing files.
- Start the Apache Sol by executing the following command:
<solr-home>/bin/./solr start -p 8983 -m 4g
- On the SAS middle tier machine, execute the following commands:
cd <sasconfig>/Lev1/Applications/SASRiskGovernanceFrameworkAdministrativeTools/dbscripts
./updateindex.sh -c <solution id>
Note: <solution_id> is based on the content solution that is being deployed. For example, for a SAS® Risk Stratum deployment, the command looks similar to the following:
./updateindex.sh -c rmc
- Start SASServer8_1 by executing the following command:
<sas_config>/Lev1/Web/WebAppServer/SASServer8_1/bin/./tcruntime-ctl.sh start