Limiting Cache for Real-Time Updates in SuiteCommerce

Limiting cache in SuiteCommerce ensures real-time visibility for website updates. Utilize cache invalidation requests effectively.

·2 min read·View Oracle Docs

To ensure your changes are reflected live on your Commerce web store, it's crucial to manage content caching effectively. Implementing Content Delivery Network (CDN) caching can enhance performance, but it may lead to outdated content being displayed. Thus, knowing how to limit the cache is essential.

How to Bypass CDN Cache

During development and testing, the following methods allow you to bypass CDN caching to see your updates immediately:

  • Domain without CDN caching: Use a sandbox account for a domain that does not have CDN caching enabled. For details on setting up a sandbox account, reference the relevant documentation.

  • Subdomain without CDN caching: Set up a subdomain linked to your main production account, ensuring it follows the pattern development(substring)._domain_._top-level domain_. For example:

    • development.example.com
    • development2.example.com
    • development-temp.example.com

This approach allows you to quickly verify changes without encountering cached content.

Cache Invalidation Requests

When changes happen, such as banner updates or modifications in style sheets, utilize cache invalidation requests. Here’s how you can manage this effectively:

  • Clear Cache for the Whole Domain: If significant changes have been made, this option helps wipe the cache across the entire domain. It's particularly useful if you're unsure of all the specific URLs that need updating.
  • Clear Cache for Specified URLs: To target specific content updates, such as an actively changing banner, submit a cache invalidation request for the URL that defines that content, e.g., /page.ss for SSP files.

How to Create a Cache Invalidation Request

  1. Navigate to Commerce > Content Management > Cache Invalidation Requests > New to open the Cache Invalidation Request page.
  2. In the Available Domains list, select the domains where you want to invalidate the cache, ensuring at least one is chosen.
  3. Decide the operation type:
    • Clear cache for the whole domain: This clears all cached data across the selected domain(s).
    • Clear cache for specified URLs: Specifically target content needing updates.

By implementing these strategies, you can maintain control over cache behavior, ensuring users always see the latest content on your website, enhancing the user experience and operational efficiency.

Summary of Topics Related to Caching

  • [Enable CDN Caching] - Understanding how to set up caching.
  • [Cache Invalidation] - Best practices and guidelines for managing cache effectively.
  • [CDN Caching for Secure Domains] - Insights into handling secure domains with CDN caching.

Frequently Asked Questions (4)

How can I bypass CDN caching during development in SuiteCommerce?
You can bypass CDN caching by using a domain or subdomain that does not have CDN caching enabled. This can be set up in a sandbox account or by configuring a subdomain structured as development.example.com.
What is the process to create a cache invalidation request in SuiteCommerce?
To create a cache invalidation request, navigate to Commerce > Content Management > Cache Invalidation Requests > New. Select the domains in the Available Domains list where you want to invalidate the cache, and choose between clearing the cache for the whole domain or for specified URLs.
When should I clear the cache for the entire domain versus specific URLs in SuiteCommerce?
Clearing the cache for the entire domain is recommended when significant changes have been made, and you're unsure of all specific URLs that need updates. Clearing the cache for specified URLs is more efficient when targeting specific content, such as frequently changing banners.
Is it possible to see updates immediately without CDN caching in SuiteCommerce?
Yes, you can view updates immediately by using a domain or subdomain without CDN caching, ideal for development and testing purposes. This ensures you don't encounter cached content.
Source: Limiting Cache Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Commerce

View all Commerce articles →