Configuration and Administration
glog.cache Properties
To control the behavior of Oracle Transportation Management, you can change settings in the glog.properties file or the appropriate property set.
Note: For any of the properties ending in .capacity, setting the value to -1 indicates unlimited capacity.
Property |
New in Version |
Description |
---|---|---|
|
Provides the ability to specify the size of the cache identified by <name>. Larger cache sizes may help improve performance in some cases, but also increase the amount of memory being used. |
|
6.0 |
Applies to cache of type LRU. Specifies the time in seconds after which an item could be removed from an LRU cache. |
|
6.4.3 |
Provides the ability to control cache size. The bigger the cache size, the faster the continuous move rating process will run. However, if the cache is too big, the system can run into memory issues. Default size: 1000 |
|
6.4.3 |
This indicates the number of seconds to wait before timeout when expiring the cache. Default = 7200 |
|
6.2 |
Provides the ability to control cache size. The bigger the cache size, the faster the algorithm will run. However, if the cache is too big, the system will run into memory problems. This is process based cache which will disappear after the process is finished. Default: 40000 |
|
22C |
Provides the ability to control the cache size for the enhanced bulk plan graphical diagnostics. The smaller the cache size the faster the the diagnostics load whe not alread cached. Default: 3 |
|
|
This cache is used when the "Distance Type" on the Rate Distance is "Lookup" and the Cache Control Type on the "External Distance Engine" is "Cache By Address Lookup And Save". Default: 40000 This is not the same as glog.cache.RateDistanceCache.capacity. |
|
|
Line Approval Tolerance Rules used by the Invoice Approval process. |
|
6.3 |
The frequency, in seconds, for checking LRU cache item expiration. |
|
|
Mail files are stored in a Least Recently Used cache. If the capacity of the cache is reached, oldest files are removed and become unavailable to the mail recipient. |
|
|
This cache is used when the "Distance Type" on the Rate Distance is not "Estimate" and the Cache Control Type on the "External Distance Engine" is anything other than "Cache By Address Lookup And Save". |
|
6.3.6 |
Provides the ability to control cache size. The bigger the cache size, it can accommodate many parallel bulk plan executions to use this cache. Each bulk plan have Rate Inquiry - Network Rate and Route
Default is 100. |
|
6.3.6 |
This indicates the number of seconds to wait before timeout when expiring the cache. Default is 7200. |
|
|
For LRU file cache, specifies the capacity of the cache. If the cache capacity is exceeded, old reports will be removed. As this may invalidate email links to reports, a customer should determine how long his recipients may take to view reports and how many reports/day are generated. He should use these data to set the capacity > reports/day * view length. Default: 200 |
|
|
Controls how many users can simultaneously access the server via cached connections. Default: 30 |
|
6.3.5 |
Provides the ability to control cache size. The bigger the cache size, the faster the compute transit time process will run. However, if the cache is too big, the system will run into memory problems. Default = 1000 |
|
6.3.5 |
This indicates the number of seconds to wait before timeout when expiring the cache. Default = 7200 |
|
|
Specifies the cache size for the stylesheet content maintained in memory. |
|
6.2.1 |
This is the capacity for storing maximum number of objects of voyages by port location for a given month. This makes it easy to get all the voyages from a given port for certain dates. |
|
|
Controls the cache size of XML templates. Default: 30 |