Cache Invalidation Process and Best Practices in NetSuite

Cache invalidation is a crucial aspect of managing content delivery in NetSuite, allowing administrators to ensure that users access the most up-to-date information. When data is cached, it typically stays in the cache until it expires. However, if data at the source changes, administrators may need to clear the cache preemptively using the Cache Invalidation Request form. This ensures that end-users receive the latest content.

How to Manually Initiate Cache Invalidation

To manually clear the cache, follow these steps:

1. Navigate to the Cache Invalidation Requests page: Go to Commerce > Content Management > Cache Invalidation Requests > New.
   You will be directed to the Cache Invalidation Request page.

2. Select Domains: Choose one or more domains from the Available Domains list to invalidate the cache for those domains.

3. Choose the Operation: Decide whether to clear the cache for the whole domain or just specific URLs. This option is essential if you've made several updates or changes to content.

   • Clear cache for whole domain(s): Use this for broader updates.
   • Clear cache for specified URLs: Target specific SSP or SuiteScript files that need updating. For example, if you frequently change a website banner, submit a cache invalidation request using the specific URL of the associated SSP file (e.g., /page.ss).

Automatic Cache Invalidation

In some situations, an automatic cache invalidation will occur, meaning you don’t need to manually initiate it. This typically happens when:

• Content of a hosted file is modified.
• A hosted file is overwritten.

However, moving, deleting, or renaming files does not trigger automatic invalidation. You can check the Cache Invalidation Status page to track the status of all requests and filter for automatically triggered ones.

Important Note: While cache invalidation updates the server-side cache, it does not impact the browser cache. Consequently, new visitors see updated content immediately, while returning users may continue to see outdated content until their browser cache clears.

Group Cache Invalidation

For performance efficiency, group cache invalidation requests can be created under specific scenarios such as when files are uploaded via SOAP web services or when a .zip file is uploaded to the File Cabinet. When multiple path invalidation requests meet a certain threshold, they may be consolidated into a single wildcard invalidation request, simplifying the management process.

Key Considerations

• Plan Regular Invalidation: Regular invalidation is necessary for frequently changing content.
• Monitor Cache Status: Frequent checks on the Cache Invalidation Status page can assist in identifying if manual invalidation is necessary.

By understanding and effectively managing cache invalidation in NetSuite, administrators can ensure that their Commerce web store delivers an optimal user experience that reflects the most current content available.

Source: This article is based on Oracle's official NetSuite documentation.