Configuring AquaLogic Commerce Services
46 BEA AquaLogic Commerce Services Deployment Guide
o productrecommendations - the element containing product recommendation
settings
productrecommendations.numorderhistorymonths - the number of
months of previous order history that is used in product recommendation
calcuations
productrecommendations.maxrecommendations - the maximum number
of recommendations that will be computed for each product
Setting either value to -1 prevents recalculation of the product
recommendations. However, existing recommendations will NOT be removed as
a result of setting the value to -1.
hibernate-config.xml
See the Storefront hibernate-config.xml section for the details on configuring hibernate-
config.xml for both the Storefront and Commerce Manager.
quartz.xml
The quartz.xml file is used to configure regularly scheduled jobs. See the Storefront quartz.xml
section for a description of the basic structure of a quartz.xml file.
Commerce Manager Quartz Jobs
The Commerce Manager has three configured jobs:
• indexBuildJob – builds the lucene search index
• productRecommendationJob – recomputes product recommendations
• topSellerJob – determines the latest top selling products
Building the Lucene Search Index
• The index build process will pick up all added, modified, and deleted objects since the last
build and update the index accordingly.
Since orders cannot be deleted from the system, the index build process won't
pick up deleted orders.
• Commerce Manager index build scheduling should normally have a shorter lag time than the
Storefront to ensure the index is as up-to-date as possible. The default setting is to start the
first build 5 seconds after application server started and then build every 5 seconds.
• Indexes are created under the following subcategories of the application WEB-INF directory:
