Deploying content to Fredhopper
The following information provides an overview of how and where content is published and processed in your Fredhopper environment. For detailed information on the Fredhopper directory structure, refer to the Fredhopper Learning Center.
Your Fredhopper <BASE_DIRECTORY>/data/instances/ directory contains subdirectories for each instance you have defined in the topology.txt file.
For example, in a demo environment you will have an Index Server (basically your database) and a Query Server instance (for querying your database): Therefore, the following topology.txt file:
<INDEXER>|localhost|1|-|Indexer and Preview environment for demo setup
<QUERY>|localhost|2|<INDEXER>|Live Query Server for demo setup
<INDEXER>is the name of your Index Server instance<QUERY>is the name of your Query Server instance
Results in the following directories when you create your Fredhopper cluster:
<BASE_DIRECTORY>\<INDEXER>and subdirectories<BASE_DIRECTORY>\data\instances\<INDEXER>and subdirectories<BASE_DIRECTORY>\data\instances\<QUERY>and subdirectories
When you publish content from the Content Manager to a Fredhopper system:
- The Content Deployer puts the XML files into the <BASE_DIRECTORY>\<INDEXER>\data\fas-xml-incremental\<CATALOG01> folder, where
<CATALOG01>is the name of your default universe. - Fredhopper moves the files to the <INDEXER>\data\xml\incoming\batch folder and processes them using, by default, the
STJob.kjbfile. - When processed, the files are put in the <INDEXER>\data\xml\incoming\processed folder when finished.
When reindexing data, you need to put the \processed files in the <BASE_DIRECTORY>\<INDEXER>\data\fas-xml\<CATALOG01> folder.