DbclassCache.properties.*
Use the customer_overrides.properties file
to override properties in dbclassCache.properties.*.
The dbclassCache.properties file contains a list of the Sterling Order Management System Software tables and the associated DBCache class. Every table listed will be registered with the cache manager with the default cache sizes. The dbclassCache.properties file also contains the global settings for the DBCache classes, and additional properties that can be uncommented and set as needed. Do not make changes directly to the dbclassCache.properties file; instead, use the customer_overrides.properties file.
| Property | Values | Description |
|---|---|---|
| sci.globalcache.select.size | Any positive integer, defaults to 10000 | Default maximum size of the “select” database cache for a given table. This is the number of select statements that return a single record that will be cached. |
| sci.globalcache.list.size | Any positive integer, defaults to 10000 | Default maximum size of the “list” database cache for a given table. This is the number of select statements that return a multiple records that will be cached. |
| sci.globalcache.count.size | Any positive integer, defaults to 10000 | Default maximum size of the “count” database cache for a given table. This is the number of select statements that count records that will be cached. |
| sci.globalcache.object.size | Any positive integer, defaults to 10000 | Default maximum size of the “object” database cache for a given table. This is the total number of resulting database objects across the “select” and “list” caches that will be cached. If this limit is reached, all database caches for the table are dropped |
| cacheManager.forcesyncloading | Valid values = true or false Default = true |
When set to true (the default), this property
forces the synchronized loading of objects in the cache from a given
entity. Concurrent threads cannot perform GET on a given entity simultaneously. To unsynchronize the loading of objects in the cache, set cacheManager.forcesyncloading to false in the customer_overrides.properties file. For example:
|
The dbclassCache.properties file also lists the cacheable tables, in the form of <TableName>.class=<cache implementation>. This would only be changed/added by applications.
Each table also supports overriding the defaults provided in the globalcache settings. For example, using YFS_COMMON_CODE as the table name:
| Property | Values | Description |
|---|---|---|
| YFS_COMMON_CODE.enabled | true or false. Default value is true. | Whether the database cache is enabled. Set to false to disable caching. |
| YFS_COMMON_CODE.select.size | Any positive integer, defaults to value of sci.globalcache.select.size | Override the “select” cache size for the given table. |
| YFS_COMMON_CODE.list.size | Any positive integer, defaults to value of sci.globalcache.list.size | Override the “list” cache size for the given table. |
| YFS_COMMON_CODE.count.size | Any positive integer, defaults to value of sci.globalcache.count.size | Override the “count” cache size for the given table. |
| YFS_COMMON_CODE.object.size | Any positive integer, defaults to value of sci.globalcache.object.size | Override the “object” cache size for the given table. |