BusinessEvents ships with default values set for basic caching functionality, so all you have to do to enable caching in a project is give the cluster a name that is used in all nodes, and enable the multi-engine feature property.
Behind the simple setup is a set of configuration properties with default values. The Learning Points section below provides information on some configuration options that you don’t have to set for the tutorial.
Node discovery The following default settings are used for multicast node discovery. Properties do not have to be added to the property files unless you use different values.
To avoid possible collisions with other clusters running on your network, the tutorial uses a non-default cluster address. More cluster discovery settings are available for different situations, such as hosts with multiple NICs. Another method of discovering nodes, using well-known addresses for situations where use of multicast is not an option.
Cache cluster features Many characteristics of the cache cluster and caching scheme are specified by properties set in the engine properties file, such as the cluster name. More in depth customization is possible but is not often required and is not documented. Contact TIBCO support for assistance.
Multi-engine features Multiple engines can run concurrently against the same project ontology. You can use a mixture of differently configured agents and identically configured
agent groups (see
Configure Inference Agents). By default the multi-engine features are disabled, so that only the agents in one EAR file (that is, running in one JVM) are active at one time. To turn on multi-engine features, which offer load balancing (and implicit fault tolerance), you set the
be.engine.cluster.multiEngineOn property to true.
Number of cache servers to start You must also set a property that defines the number of cache servers to start before starting any inference agents. The
be.engine.cluster.minCacheServers property ensures that the cache is populated before inference agents begin processing events.