Base Source Cache Properties Dialog Box

Getting there

The following three options apply to the base source:

Cache parent directory (enables update caching for this source)

Enter the name of a directory where you want to store cache files. Cache files will be stored in the sourcename subdirectory of the parent directory specified here. For example, if the source is named BANKDB and the parent directory is D:\DATABridge\Cache, then the cache files will be stored in the D:\DATABridge\Cache\BANKDB subdirectory.

In addition to setting the Cache parent directory, you must complete other steps before caching can start. See Caching.

When tracking, read cached files

Specify whether cached files can be read while tracking and if a user name and password are required to read them.

To require a user name and password to access the cache, select If available or Only. This information is stored as encrypted text within the Windows registry.

Note: If Never or If available is selected, once Enterprise Server has read everything in the cache for the base source, it searches for additional updates in the original MCP-based audit files.

 

If available

This setting causes Enterprise Server to rely on audit files that have been previously cached. When all of the available cache for the base source has been processed by the client, Enterprise Server reads the host audit files for more audit information.

 

Only

This setting causes Enterprise Server to rely exclusively on the cached audit files for the base source. Clients will only read from the Enterprise Server stored cache and not add to the mainframe load.

 

Never

This setting causes Enterprise Server to ignore any cached audit files for the base source and always read the host audit files. This is useful for testing access to non-cached audit files.

Remove cache files when read n times

Enter the number of DATABridge clients you expect to read this cache. For example, if you know that three clients will access this cache, enter 3. Enterprise Server will remove the cached audit file after it has been read three times.

Important: This option applies only to DATABridge Clients that read the base source rather than a local source. If no Clients read the base source, the cache files for the base source must be removed manually.

Options that apply to this source and its local sources

Both before-images and after-images for modifies

Select this check box to store the before- and after-images for modified records. When this check box is cleared, before-images aren't stored (which results in smaller cache files). Clearing this option does not allow for scenarios where the key of a record is changed.

Wait for audit to cache

Select one of the following options to determine how long Enterprise Server waits before checking for more updates:

 

Don't wait

Enterprise Server terminates when no more audit is available (no retries)

 

Wait forever

Enterprise Server does not stop checking for additional audit (unlimited retries).

 

Wait max seconds

Enterprise Server terminates if no audit is available for the period set in Max seconds.

Max seconds

Applies only if you select Wait max seconds.

Enter the maximum number of seconds you want Enterprise Server to wait for more audit.

A value of 100 limits the number of consecutive failed retries so that the total time for all of the failed retries won't exceed 100 seconds. For example, if Seconds between retries is 5 and Max seconds is 100, Enterprise Server will check every 5 seconds up to 20 times before quitting because there is no more audit available. A value of -1 is the same as selecting the Don't wait setting. A value of 0 is the same as selecting the Wait forever setting.

Seconds between retries

Applies only if you select Wait forever or Wait max seconds.

Enter the number of seconds you want Enterprise Server to wait before it checks again for more audit.

If additional audit is not available within the time specified in the options, you will need to re-initiate caching. See Ways to Initiate Caching.