Experience Optimization DTAP infrastructure
When implementing Fredhopper (FAS), it is recommended to use "Preview", "Intermediate", and "Live" servers to manage the development process and replicate data (configuration and indexes) between these servers.
Fredhopper uses a concept of Preview and Live data to manage the development process. Fredhopper recognizes two kinds of data:
- Indexes refer to the raw data (used in promotions) and how it can be accessed and manipulated
- Configuration is the business data defined in the Business Manager.
The diagram shows the following:
- Content Manager
- Promotional content is created and stored in the Content Manager. The Content Manager items used to create the data (Schemas, Templates and Components) are ported within the DTAP infrastructure just like any normal Content Manager items using Content Porter.
- Fredhopper Preview Server
- The Preview Server is where marketeers create promotions and perform all configuration changes. The Preview Server receives promotional content created and published from the Content Manager. Marketeers replicate the business configuration to the "Intermediate" server.
- Fredhopper Intermediate Server
- The Intermediate Server receives configuration updates from the Preview Server and live promotional content created and published from the Content Manager. The data on the Intermediate machine is the data that is also live on the Web site.
- Fredhopper Live Server
- The Live Server handles user requests from the Web site to the Fredhopper Application Server. It receives configuration and index update from the Intermediate Server. You can scale out the Live Servers.