You can use multiple mechanisms to update the data in the Unwired Server cache.
The cache can be refreshed using the apply results cache policy (cached data corresponding to operation results is updated immediately based on data from the device, without invalidating the cache). Other cache policies include the invalidate cache policy (a restrictive policy that only updates specific cache partitions), and the no cache update policy (an operation has no effect on the consolidated database).
Developer and application administrators can also either define cache updates based on a schedule that can be set using an interval, or more granularly by setting days, dates, and specific times for refresh.
Also, for cases where the cache refresh may be expensive due to volume, you can use the data change notification (DCN) option to propagate changes from the back-end enterprise information system (EIS) to the Unwired Server or HTTP/HTTPS interface for any MBO. If you use DCN, you should not use a scheduled refresh. The DCN mechanism can also used to initiate a server-initiated workflow.
The DCN payload containing changed data is applied to the cache and the change gets published to subscribing device users based on a change detection interval time. This option is the least intrusive and most optimal for addressing high-load environments and optimizing the load on the EIS data sources to keep the Unwired Server cache consistent.