Refreshing the registry

If you need to refresh the registry, there are several ways you can do it. You can use the DynaCacheInvalidation command, create a scheduled job to run after the stagingprop utility, or call the refresh registry process by URL.

Refresh the registry with the DynaCacheInvalidation command

To ensure that your registries are refreshed and your updated content is displayed, you can run the DynaCacheInvalidation command. Be sure that the enableRefreshRegistry parameter is set to true. When this parameter is true, the DynaCacheInvalidation schedule job inspects each value in the DATAID column of the CACHEIVL database table. If the values in this column are in the form WCR+<registryName>, the scheduler job adds a broadcast scheduler job. This addition causes the specified registry to be refreshed on each currently running Transaction server. For more information, see DynaCacheInvalidation URL.
Tip: If the values in this column are in the form WCR+?, the scheduler job adds a broadcast scheduler job. This addition causes all registries to be refreshed on each currently running Transaction server.

Create a scheduled job to run after the stagingprop utility

If you ran the stagingprop utility to propagate changes and now you need to refresh the registry. After you propagate changes from an authoring instance to a production live instance, you need to refresh the registry before some updates display in your store. For instance, if your live instance store includes running web activities or e-Marketing Spots, you need to refresh the registry.

You can create a scheduled job to run after the stagingprop utility runs to refresh the registry whenever the stagingprop utility runs. For more information, see Scheduling a site-level job.

For more information about running the stagingprop utility, see Stagingprop utility.

Call the refresh registry process by URL

You can also refresh the registry by calling the refresh registry process by URL. You can include the RefreshRegistry parameter within a URL request for logging in to your live instance store. With this URL request, you need to first call the login process to authenticate your user account, and then the URL can redirect to the refresh registry URL and begin the refresh.

  • For example: 
    https://host_name.com/webapp/wcs/stores/servlet/Logon?logonId=user_name&logonPassword=user_password&URL=RefreshRegistry?URL=TopCategoriesDisplay
    Where:
    host_name
    The host name for your live instance store where you need to refresh the registry.
    logonID
    The logon ID for the user account that you use to log in to your store.
    logonPassword
    The plain text password for your user account.
    Important: This approach uses a password that is in plain text.
    For more information, see: