Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Object Management Configurations

To configure object management for your application, select the store provider, cache provider, configure a cache agent quorum, and number of back-up copies.

If you have a backing store, you can also configure a limited cache and specify the cache size for each entity.

## Configuring a 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 startup.

## 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.

Note: Use of limited cache is supported only when a backing store is used. The backing store retains entries in excess of the limit. Without the use of a backing store data inconsistency could result:

- 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.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.