Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. The Developer Center continues to support Commerce 6.13.0 through 7.4.1.Visit new site

Scheduled Jobs (Commerce Manager)

Scheduled Jobs (Commerce Manager)

The commerce server uses scheduled jobs to perform certain operations, such calculating top selling products and product recommendations. The quartz.xml file contains settings that configure how and when these jobs run. It is located in the cmserver/ep-cmserver/src/main/resources/spring/scheduling directory.

Commerce Manager Server Quartz Jobs

The Commerce Manager server has the following jobs:

  • topSellerJob determines the latest top selling products.
  • productRecommendationJob recomputes product recommendations.
  • processImportJob
  • importJobCleanupProcessorJob
  • staleImportJobProcessorJob
  • cleanupOrderLocksJob
  • cleanupSessionsJob purges customer sessions with empty shopping carts from the storefront.

Computing Product Recommendations

A trigger is declared for computing product recommendation data. A SimpleTriggerBean is typically used to compute recommendations every 30 seconds for demonstration purposes. For production, a CronTriggerBean should be used to compute recommendations with a longer interval such as one day.

Note:

Running the product recommendations job frequently on a large catalog with many orders can have a negative impact on performance. In a busy production environment, it is recommended that you schedule it to run at intervals of one hour (3600000 milliseconds) or more.

Computing the Top Sellers

A trigger is declared for computing the top selling product statistics. A SimpleTriggerBean is typically used to compute recommendations every 30 seconds for demonstration purposes. For production, a CronTriggerBean should be used to compute recommendations with a longer interval such as one day.

Note:

Running the top sellers job frequently on a large catalog with many orders can have a negative impact on performance. In a busy production environment, it is recommended that you schedule it to run at intervals of one hour (3600000 milliseconds) or more.