![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
• Object Persistence Enables objects to be available for reuse, either in memory caches or in databases. Objects can also be recalled into the Rete network, thus extending the possible functionality of your system.
• Data Recovery Ability to survive failures without loss of data.
• Object Partitioning The ability to partition the objects among multiple JVMs. and to handle notifications of object additions, deletions, and changes to all the agents, enabling them to remain synchronized.
• Object Clustering The ability to maintain multiple copies of each object in different nodes (JVMs) such that if one node fails, another node can take over.
• Message Acknowledgement See Message Acknowledgement for information on the way each object management type handles message acknowledgement.
TIBCO BusinessEvents Express Content relating to Cache OM and backing store is not relevant to TIBCO BusinessEvents Express edition.A more complete introduction to the terms is located in Distributed Cache and Multi-Agent Architecture and Terms. However, the following basic definitions are used in other (prior) sections.Processing Unit A processing unit deploys as a TIBCO BusinessEvents engine. One engine runs in one JVM.Agent Each processing unit contains one or more agents of different types. The main types are inference agents, which perform the inferencing work, and cache agents, which manage the objects.Agent Class An agent class is a configured agent definition. Configuration specifies, for example, what channels, startup rule functions, and rules the agent will use at runtime. You can deploy multiple instances of the same agent class, and you can deploy instances of different agent classes, depending on the work the application is designed to do.Cache Agent An agent that stores cache data. A processing unit can have one cache agent only. (Processing units that run other types of agents can have cache storage enabled too, which can be useful for demonstration purposes only, but not in production systems).Seeders and Leeches (TIBCO BusinessEvents DataGrid terms) A seeder is an agent that stores cache data. Cache agents are seeders by default. A leech is an agent that is part of the cluster but does not store data. Agents other than cache agents are generally leeches. These terms are not generally used in the documentation. However they may be useful to know about for technical discussions.Cache OM offers fine-grained object management controls at the object level. See Chapter 7, Distributed Cache OM.For implementation details, see TIBCO BusinessEvents Developer’s Guide.
For Fault Tolerance In Memory OM itself does not support fault tolerance. If you require fault tolerance with an in memory system, then configure for Cache OM, but use the Memory Only mode for all objects. Because data is not persisted, it is lost during failover and failback. However, the engine process continues.
Perform tests after changing object management type As with any change in configuration, be sure to perform thorough testing before going into production.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |