Caching schemes determine the specific characteristics and behavior of the cache. The provided schemes have been configured for BusinessEvents use. Common configuration options are available using properties (see Configuring Caching Scheme, Multi-Engine, and Cluster Properties). In most cases there is no need to be aware of the caching scheme that underlies your configuration options.All caching schemes are for a distributed cache, which has been determined to be the best option for BusinessEvents. The table below provides basic information in case you need to work with Support to configure the caching scheme options beyond the provided configuration options.Backing Store Schemes Use Write-BehindBusinessEvents performs backing store operations in bursts after each RTC. Write-behind is used for both backing store schemes, with a write-delay of one second. With write-behind, which is asynchronous, set the JDBC connection pool size to match (or exceed) the number of entity types you expect to modify. Each entity type has its own write-behind queue.
Table 38 Provided Caching Scheme Names Distributed cache with backing store and no expiry and eviction.Requires implementation of a backing store. Distributed cache with backing store and limited entries (for use with backing store only. If you don’t use backing store, use a scheme with unlimited entries)Requires implementation of a backing store. Distributed cache with no backing store and no expiry and eviction
Copyright © TIBCO Software Inc. All Rights Reserved.