System Information in v5.2

Installing and Configuring DocuNECT v5.0

---

The System Information section in v5.2, has the following two options:

1) Applications Log
2) Cache

---

Application Log

All errors that occur within the DocuNECT web application are stored in the Logs sub-menu option in the Administration menu.

Click on the error link to display the details:

---

Object Cache

DocuNECT Web includes a cache for the following objects: Cabinets, Stations, Storage Locations, Roles and Users.
The table in the Cache section displays the current cache information

Note, cache settings can be configured from web.config.

<cacheSettings>
        <globalSettings>
            <add key="Enabled" value="True" />
            <add key="LoggingEnabled" value="True" />
            <add key="StatisticsEnabled" value="True" />
        </globalSettings>
        <cabinetsSettings>
            <add key="Enabled" value="True" />
        </cabinetsSettings>
        <rolesSettings>
            <add key="Enabled" value="True" />
        </rolesSettings>
        <stationsSettings>
            <add key="Enabled" value="True" />
        </stationsSettings>
        <storageLocationsSettings>
            <add key="Enabled" value="True" />
        </storageLocationsSettings>
        <usersSettings>
            <add key="Enabled" value="True" />
        </usersSettings>
</cacheSettings>

Column	Description
Cache Name	The cache object.
Enabled	Indicates the cache is enabled or not. When the cache is disabled, the requests are going directly to the database.
Total Items	The number of items in cache.
Hit Rate	A percentage value computed from = cache hits / (cache hits + cache misses) * 100.
Miss Rate	A percentage value computed from = cache misses / (cache hits + cache misses) * 100. A cache miss occurs when the requested object is not already loaded in cache, or the item has expired.
OpName	The name of the operations that we are making statistics for. Deletes - The action of deleting an item from cache. Fetches - A fetch occurs when the loader is invoked for an item that does not exist in cache, bringing the item from the database to the cache. The fetch time is the time required to get the item from database to cache. Hits - A hit occurs when the object is requested from cache and it is found. Inserts - The action of adding an object to the cache. Misses - A miss occurs when the object is requested from cache, but it does not exist or it has expired. Updates - An update occurs when an existing item (uniquely identified by its key) is updated in cache (because its properties have changed). Waits - A wait occurs, when an item does not exist in cache, and the loader is already executing. The loader executes a single time per key, concurrent requests for the same key are waiting for the first request to complete. The number of waits is expected to be zero in case of low concurrency usage.
OpCount	The number of times the operation was recorded since last statistics reset.
OpAvgTime	Average time per operation. The value is computed in CPU ticks which gives the best precision but gives little information to the user. Maybe we should change it to milliseconds or something.
Speed Factor	The factor indicates how much faster the cache responds compared to getting the data directly from database. SpeedFactor = DatabaseTime / CacheTime Where: DatabaseTime = averageTime (fetch) CacheTime = hitRate / 100 * averageTime(hit) + missRate / 100 * averageTime(miss + delete + fetch + insert)

Refresh Cache Statistics

You can set the automatic refresh time below the cache table to monitor the statistics, or you can refresh the cache statistics by pressing the Refresh Now button.

Clear Cache

Pressing the Clear Cache button removes all the objects from the cache. The objects will be reloaded from database when requested for the first time.