Object Management Configurations
To configure object management for your application, select the store provider, cache provider, configure a cache agent quorum, and number of backup copies.
If you have a backing store, you can also configure a limited cache and specify the cache size for each entity.
Configuring Cluster Provider
- Configuring TIBCO FTL as the Cluster Provider
- Configuring Apache Ignite as the Cluster Provider
- Setting Up Legacy ActiveSpaces as Cluster and Cache Provider
Configuring the Backing Store
- For backing store related project configuration details, see Persistence Options.
- For details about setting up the backing store itself, see TIBCO BusinessEvents Administration.
Configuring Management of Domain (Entity) Object Instances
If you choose Cache OM or Store OM, you must also configure how to manage the domain (that is, entity) object instances.
For example, you can determine whether the instances are flushed from the Rete network after each RTC (as is generally recommended) or are kept in the cache.
If you set up a backing store, you can specify additional settings. For example you can define a subset of ontology object instances to be stored in the backing store, and you can control which (if any) object instances are loaded into the cache from the backing store at system start up.
Configuring a Limited (or Unlimited) Cache
You can use the options available to configure a cache of a limited size, or use the described procedure to set options for an unlimited cache.
Also see Limited and Unlimited Cache Size in TIBCO BusinessEvents Architects Guide.
- Entries for an object in the object table (an internally used cache) and in the object cache itself could expire independently of each other.
- Domain object settings for limited cache apply at the object level. Related concepts could have different settings. For example, a container concept could have a limited cache setting and its container concept an unlimited cache setting. Each could be evicted at different times.