CDD Configuration

To configure object management for Cache OM, select the 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.

Use this chapter if you picked Cache OM in the second page of the New Cluster Configuration wizard. This chapter explains how to configure cluster discovery and internal communications, and how to configure cache-related object management settings.

In addition to the basic reference tables (as noted in the procedure below) the following sections have additional specific guidelines:

Configuring the Backing Store

For backing store details, see CDD Backing Store for project configuration details and see JDBC Backing Store for details about setting up the backing store itself.

Configuring Cache OM Options

To configure cache OM options, first add a CDD file (or open the CDD file you added). Then select the Cluster tab > Object Management node on the left and on the right, configure settings as explained in CDD Cluster Tab and Cache OM Settings Reference.

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 Architect’s Guide.

Note:
Use of limited cache is supported only when a backing store is also used
The backing store retains entries in excess of the limit. Without use of a backing store data inconsistencies 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.