Documentation Center

Upgrading Fredhopper Access Server (FAS)

Make a capture your configuration files and upgrade your FAS to the latest version of the Fredhopper Deployment Package. You then need to reinstall your configuration files and install the SmartTarget API extensions and Kettle job.

Before you begin

This task summarizes the instructions for installing the Fredhopper Deployment Package: refer to the Fredhopper Learning Center for detailed information, including prerequisites.

Procedure

  1. Stop the Index Server by running the following command, from the fredhopper\instance\FAS directory, in a command prompt:
    bin\stoploader
  2. Stop the Query Server by running the following command, from the fredhopper\instance\FAS directory, from the command prompt:
    bin\qserver stop
  3. Capture the instance configuration:
    • On Windows, run the following command:
      bin\capture -d <PATH>/SmartTarget_upgrade.zip -c 
    • On UNIX, run the following command:
      bin/capture -d <PATH>/SmartTarget_upgrade.zip -c 
    where:
    • <PATH> is the file system folder where you want create the file to use. Ensure that the output folder exists.
    • SmartTarget_upgrade.zip is the name of the ZIP file you want to create.
  4. Rename your Fredhopper installation folder.
  5. Download and install the Fredhopper Deployment Package.
  6. Edit your topology.txt file, for example:
    <INDEXER>|localhost|1|-|Indexer and Preview environment for demo setup
    <QUERY>|localhost|2|<INDEXER>|Live Query Server for demo setup
  7. Run the following command to start your deployment agent:
    bin\deployment-agent
  8. Run the following command to create your Fredhopper cluster:
    bin\setup-cluster
  9. Create the following directories:
    1. In the <BASE_DIRECTORY>\data\instances\<INDEXER> directory, create a directory called \custom.
    2. In the <BASE_DIRECTORY>\<INDEXER>\data\fas-xml-incremental\ directory, create a directory called the name of your universe, for example:
      <BASE_DIRECTORY>\<INDEXER>\data\fas-xml-incremental\<CATALOG01>
    3. In the <BASE_DIRECTORY>\<INDEXER>\data\fas-xml\ directory, create a directory called the name of your universe, for example:
      <BASE_DIRECTORY>\<INDEXER>\data\fas-xml\<CATALOG01>
  10. Import the instance configuration:
    • On Windows, run the following command:
      bin\capture-import <INDEXER> <PATH>/SmartTarget_upgrade.zip
    • On UNIX, run the following command:
      bin/capture-import <INDEXER> <PATH>/SmartTarget_upgrade.zip
  11. Delete the styles folder in the following location:
    <BASE_DIRECTORY>\data\instances\<INDEXER>\config\styles
  12. Go to your old Fredhopper installation and copy the XML files in the following directory:
    fredhopper\instance\FAS\data\xml\processed\batch
    Paste the files into the following folder:
    <BASE_DIRECTORY>\<INDEXER>\data\fas-xml\<CATALOG01>
  13. Install the API extensions:
    1. Access the SmartTarget installation media.
    2. In the Fredhopper extensions folder, copy the following JAR files to the \custom directory:
      • smarttarget_api_extension.jar
      • configuration-management-rest-extension.jar
      <BASE_DIRECTORY>\data\instances\<INDEXER>\custom
  14. Add the Kettle job to your Fredhopper installation:
    1. Access the SmartTarget installation media.
    2. In the Fredhopper extensions folder, copy the STJob.kjb file to the following directory:
      <BASE_DIRECTORY>\data\instances\etl
  15. Run the following command to recreate the index:
    bin\reindex <INDEXER>
  16. Publish a business configuration file:
    1. Open the Fredhopper Business Manager.
    2. In the main screen, click the File button.
    3. In the File this configuration screen that opens, click the File button to file the current configuration as a unique version.
    4. Access the System Manager > Management > Publication manager screen.
    5. Click the Approve button on the item that you want to export to change the status to Approved.
    6. Click the Publish button to publish the configuration.
    When you publish your business configuration it becomes active in your Live environment.
  17. Run the following command to update the configured live servers with the current index and configuration:
    bin\fresh-index-to-live <INDEXER>