Populate Cache Job

Since anonymous customers spend most of their time browsing, Digital Commerce provides the ability to populate the cache in advance to ensure their first visit is a highly productive visit. This is referred to as inorganically creating the cache. Digital Commerce does this by executing the Populate API Cache job. This job populates cache entries related to Get Offers and Get Offer Details APIs for anonymous users.

Before you begin the populate cache job, prepare your org for Digital Commerce API Caching.

  • You have created product offerings within the product designer by specifying their name, structure, pricing, attributes, etc.

  • You have created a sales catalog for the product offerings.

  • Do not modify your catalog or product offerings until you have executed all of the populate cache APIs listed in the next section. For example, do not make a Catalog Profile API call, remove products from your sales catalog, and then use the Rule Set Combinations API.

There are two ways to execute the Populate Cache jobs. You can decide which method to choose based on the size of your catalog and the time it takes to execute each job.

Avoid mixing or interrupting cache management APIs with cache management batch jobs and vice-versa. Choose a method for executing cache management and maintain a consistent execution pattern.

  • A batch process named Populate API Cache, available through the CMT Administration UI.

    Each job works by executing several different APEX jobs. The APEX jobs are executed sequentially.

  • Populate Cache API, available as REST APIs.

    These are Cache Management APIs that can make API calls in parallel, which can dramatically speed up the process of populating your cache.

The populate cache job always runs in Greenwich Mean Time (GMT) time zone. Ensure that the dates and times in your database are stored in GMT and not in your local time zone.