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 Management of Domain (Entity) Object Instances
- Cluster Discovery and Internal Communication
- Synchronous and Asynchronous Replication of Cache Objects
- Property for Cache Based Object Management on AIX
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.
- 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.
- Adding a CDD
When you add a CDD, you select an object management type (known as the OM type). - Configuring Management of Domain (Entity) Object Instances
If you choose Cache OM, you must also configure how to manage the domain (that is, entity) object instances. - Configuring Limited Cache and Object Table Cache Options
As desired, you can set the cache to limited at the default level and unlimited for specified objects; or you can set the cache to unlimited at the default level and limited for specified objects. - Synchronous and Asynchronous Replication of Cache Objects
Backup count defines the number of backup object copies to make in addition to the primary cache object. - Property for Cache Based Object Management on AIX
When TIBCO BusinessEvents is installed on AIX and uses cache-based object management, you must add the property java.net.preferIPv4Stack=true to all TRA files. - Cluster Discovery and Internal Communication
When you add a CDD file and select Cache OM type, you must configure how the members of the cache cluster discover each other at runtime and communicate with each other once the cluster is established. - Configuring a DataGrid Cluster (Metaspace)
An active LAN connection (device enabled and network cable plugged in) is required for TIBCO BusinessEvents DataGrid to work. - Configuring an Oracle Coherence Cluster
First part of the task is to add /open a CDD file and set up the properties. - DataGrid Discover URL
When a cluster starts up, and also when new members join a cluster, a discovery process enables the members to discover each other. - DataGrid Listen URL
The listen URL is used for direct communication between the members of the metaspace. It is configured the same way for multicast and for unicast discovery. - DataGrid Transport Security
Transport-level security allows you to protect data being transported within the DataGrid by preventing alteration of traffic, eavesdropping, and exchange of data between untrusted parties. - Setting Up DataGrid Security and Authentication
When security is used, any transmission of messages within the DataGrid occurs on a secure transport. A security domain's transport_security setting controls the level of security used for communication within the DataGrid. - Restricting Transport Access
Transport level security allows you to restrict transport connections within a security domain to only the “trusted” nodes. - Schema Model Migration with Shared Nothing Persistence
Using Shared Nothing persistence to migrate a schema model. - Enabling Hot Deployment of New Concept and New Concept Properties
New concept and new concept properties can be enabled for hot deployment for Cache OM with no backing store, while it is enabled by default for the shared nothing persistence. - CDD Cluster Tab DataGrid Properties Reference
DataGrid properties can be configured using the CDD Cluster Tab. Refer to the following table for a list of properties that you can use to retrieve data from the DataGrid. - Enabling Use of Oracle Coherence as the Cache Provider
If you want to use the Oracle Coherence cache provider, you must provide a fully licensed, supported version of the software. - Oracle Coherence Cluster Discovery
You can use either multicast or well-known-address (WKA) discovery, as appropriate. - Configuring Well-Known Address Cluster Discovery
You can add up to nine well-known addresses. If you need to add more refer to Coherence documentation for instructions about using override files.