Documentation Center

Reindexing data

When you make changes to the structure of promotional content in the Content Manager or you change the navigation index in Fredhopper, you need to reindex your data.

About this task

When you make certain types of changes to Fredhopper data, you need to perform a reindex Fredhopper so the changes are shown. The following are two types of changes that make reindexing necessary:

  • Schema changes in the Content Manager with subsequent updates to Components based on the schema
  • Making attributes live in Fredhopper (Fredhopper indexes data using live attributes that you have added to the Navigation Index.)

Procedure

  1. From the Fredhopper root directory, execute the following command to stop the Fredhopper instance:
    bin\instance INDEXER stop

    where,INDEXER is the name of your Index Server specified in the topology.txt file .

  2. Depending on the reason for the reindex, complete the appropriate steps in the following table.
    Cause of the reindexSteps
    Making attributes live in Fredhopper
    1. Back up the contents of the following directory:
      BASE_DIRECTORY\data\instances\INDEXER\data\xml\processed\batch

      where, BASE_DIRECTORY is the Fredhopper root directory.

      These files contain the contents of the Transport Packages published from the Content Manager to Fredhopper and converted to Fredhopper XML.

    2. Copy the files to the following directory:
      BASE_DIRECTORY\INDEXER\data\fas-xml\CATALOG

      where, CATALOG is the name of your default universe.

    Schema changesDelete the contents of the following directory:
    BASE_DIRECTORY\INDEXER\data\fas-xml\CATALOG

    where, CATALOG is the name of your default universe.

  3. Run the following command to recreate the index:
    bin\reindex INDEXER
    The existing index on the Fredhopper Business Manager is recreated.
  4. Run the following command, executed from the Fredhopper root directory:
    bin\fresh-index-to-live INDEXER
    Configured live servers are updated with the current index and configuration.

What to do next

If you performed the reindex due to schema changes, republish the updated Components. No additional steps are necessary if the reindex was due to Fredhopper live attribute changes.