![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Cache OM is a requirement for certain features such as multi-agent concurrency (as explained in Chapter 9, Concurrency and Project Design).Object management is configured using the Cluster Deployment Descriptor (CDD), an XML file that you edit in TIBCO BusinessEvents Studio using a provided editor. See Chapter 23, Cluster Deployment Descriptor (CDD) in TIBCO BusinessEvents Developer’s Guide for details.See Characteristics of a Distributed Caching Scheme for more details.Scaling is linear. To scale the system’s capacity to process more data, add more inference agents (see Inference Agents). To scale the cache, add more cache servers (see Cache Agents).In addition, each entity can have a different cache mode, to help you balance memory usage and performance (see Between Cache and Rete Network: Cache Modes).See Characteristics of a Distributed Caching Scheme for more details.
• Multiple instances of the same inference agent class, each running on different PUs, form an agent group. This provides simple load balancing of messages arriving from queues, as well as fault tolerance. You can also configure content-aware load balancing for “session stickiness.” (See Chapter 25, Load Balancer Configuration in TIBCO BusinessEvents Developer’s Guide.)
Concurrent RTC You can also enable concurrency within a single agent, using the multi-threaded Rete feature, known as concurrent RTC (and in prior releases as concurrentwm). Within one agent, multiple RTC cycles take place concurrently.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |