When you use Cache Manager and a backing store, various options help you manage where entity objects are stored, and how to retrieve them from the backing store at startup to optimize performance and memory management for your system.Although best performance is obtained when all objects are loaded into the cache, in practice there are often more objects than you can keep in the cache, or want to.You can configure what objects to preload into cache on startup, and what objects to evict from the cache when not needed in various ways and to various degrees of granularity.When considering the preload options you must also consider the role of the object table. This is explained in The Role of the Object Table.It is also important to start enough cache servers before loading begins to handle the work. See Starting a Minimum Number (Quorum) of Cache Servers.Yet another aspect of object management is loading objects from the cache into the Rete network. With Cache OM and Cache Only mode, you must load objects into the Rete network when needed, using various functions.This is discussed in Chapter 8, Cache Modes and Project Design, in TIBCO BusinessEvents Developer’s Guide.These data management settings are used with any backing store implementation.You can configure some object management controls using settings in the entity resources in BusinessEvents Studio.The entity resource settings are stored in the EAR file. CDD editor settings, however, are stored in the cluster descriptor definition file which is not in the EAR. CDD settings, therefore, override EAR settings. You don’t have to rebuild the EAR file when you make changes in the CDD file (using the editor). You do have to restart the system, however.
Copyright © TIBCO Software Inc. All Rights Reserved.