How Caching Works

Caching is best suited for sites that track multiple data sources from a single DMSII database.

Caching allows you to separate the process of filtering data from the process of delivering client-requested data. Cached files are filtered in advance, thereby allowing Enterprise Server to send data requests quickly and without placing an additional resource burden on the mainframe. (By contrast, non-cached sources are retrieved and filtered after they've been requested from the client.) The more cached local sources that you have for a single remote source, the greater the performance improvement.

In Enterprise Server, you can create one or more local sources from a single Server Accessory source. Each local source can specify its own unique filtering conditions. When caching is enabled, Enterprise Server first looks for updates that match the filter requirements of the Server Accessory source. Then, Enterprise Server applies the filtering conditions of the local source and writes the update to the local cached file.

When a DATABridge Client requests updates from a cached local source, Enterprise Server reads the updates from the cache files instead of requesting them from MCP server or reading the DMSII audit files directly.