Show Contents / Index / Search

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 delivering client-requested data from filtering that data. Cached files are filtered in advance. This lets Enterprise Server quickly send data requests without placing an additional resource burden on the mainframe.

In Enterprise Server, you can create one or more local sources from a single DBServer source. Each local source can specify its own unique filtering conditions. When caching is enabled, Enterprise Server applies the filtering conditions of the local source and writes the update to the local cached file. When you have multiple local sources for a single remote source, caching them will improve performance.

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.

Next

Setting Up a Base Source Cache