To enable caching, you must first configure a base source cache. The base source cache has additional options such as whether to cache before- and after-images.
To set up a base source cache
In the right pane of the Databridge Enterprise window, right-click a base source and click
.In the
dialog box, click [Cache].In the Base Source Cache Properties Dialog Box, do the following:
In the
box, type or browse to select the directory to which cached files are written. This box enables caching.From the
menu, specify an option to determine whether cached files can be read while tracking.From the
options, specify how long you're willing to wait for additional updates to cache.For
, enter the number of Databridge Clients you expect to read this cache. If Clients are tracking only filtered sources, only cached audit files from local filtered sources will be deleted; cache files for base sources will need to be removed manually.Select the check box
if you want to store before- and after-images for modified records. Not selecting this check box results in smaller cache files but does not allow for changes to record keys.From the
menu, select an option that determines if or how long Enterprise Server waits before checking for more updates.Click OK, and then click [Save] in the Databridge Enterprise window.
NOTE:If the
button in the Databridge Enterprise window is enabled, you have made changes that have not been written to disk and therefore are not yet in effect. To put your changes into effect, click the button.Set up a local source cache for each local source (derived from this base source) that you want to cache. If you don't have local sources you want to cache, you can populate only the base cache. When you first create a local source, all of its data set A data set is a file structure in DMSII in which records are stored. It is similar to a table in a relational database. You can select the data sets you want to store in your replicated database. except for the restart data sets are included.
If the client requests updates from a local un-cached source, Enterprise Server will read updates from the base source's cache and apply the local source's filters. A filter is a set of conditions you can define, which allows you to replicate only the data that's relevant to a particular client. See Filtering a Local Source.