Feature Pack 4Feature Pack 2Feature Pack 5Feature Pack 3Feature Pack 6

Replicating WebSphere Commerce search with the repeater

The repeater should be set up after all the remote search clusters in both Staging environment and Production environment are already configured.

Procedure

  1. In the Production environment, set up the repeater:
    1. Create a WebSphere Application Server profile and deploy the SOLR.war file. This is your new web application for the repeater.
    2. Copy all files, for example MC_file_names and solr.xml from the solrhome in the Production System over to a separate file system location accessible by the repeater. This is the new solrhome of the repeater.
    3. From the new solrhome of the repeater, modify each one of the repeater's solrconfig.xml to reconfigure for the search repeater (uncomment section 2). Then, set the master URL in this section to point to its corresponding Solr core in the master Solr server from the Staging environment.
  2. In the production environment, set up all the subordinate search servers to point to the repeater:
    1. For each of the subordinate search servers in production, modify each of their solrconfig.xml files to enable the predefined section 1, which is designed for use with subordinate search servers in production.
    2. Update the master URL in the solrconfig.xml file to point to the corresponding Solr core in the repeater.
    3. Update the SRCHCONF database table to point to the host name of the repeater. This is because pre-processing for emergency fixes is now performed in the production system and reindexing through the repeater.
    Note: Emergency updates performed on production should be duplicated on staging.
  3. For each of the master search servers in Staging, modify the solrconfig.xml to enable the predefined section 3 in the solrconfig.xml file.