CDD File for Cache Object Management and the EAR

To set up the project for cache object management, you create a new CDD file using the template provided for cache OM. The CDD template defines an inference agent class and a cache agent class, and default values for cluster level properties, so it doesn’t take much to configure an example project to work. Other configuration options are available for different situations.

Learning Points

How do I configure cluster nodes to discover each other?
 For the tutorial you can use the default multicast node discovery settings. The default settings are available only when you use Legacy ActiveSpaces as your cluster provider. You can also change the defaults as needed to avoid collisions with another cluster in the same network. Cluster discovery settings are available for different situations, such as hosts with multiple NICs. Another method of cluster discovery uses well-known addresses for situations where use of multicast is not an option.
How do I configure agents and processing units?
A processing unit deploys as a TIBCO BusinessEvents engine. At a minimum, you list the agents you want to run in one processing unit. For this example, you do not have to do any processing unit configuration because defaults will work out of the box. However, for real-world scenarios, where concurrency features are used, and perhaps add-on products, processing unit configuration requires some thought and planning.
Number of cache agents to start
 For a production environment you can define how many cache agents must be started before the system startup can continue. The default is one. When a backing store is used, cache agents can preload objects from a backing store at system startup. More cache agents make the preloading phase quicker. See the Cache Agent Quorum setting in the Object Management Configuration panel.

More Information

See TIBCO BusinessEvents Configuration Guide.