Object Management (OM)

Object management refers to various ways that TIBCO BusinessEvents can manage the ontology object instances created by TIBCO BusinessEvents.

Cache and store object management enables rich functionality and is generally chosen for enterprise applications. In Memory object management can also play a useful secondary role in testing, and as an event router.

Note: You can’t mix different types of object management in one TIBCO BusinessEvents application. For example, you cannot deploy one engine using Cache or Store OM and another using In Memory OM.

The goals of object management are as follows:

Object Persistence
Enables objects to be available for reuse, either in memory caches or in stores. 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
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
For each message type (that is, each type of channel), TIBCO BusinessEvents acknowledges the receipt of messages according to the protocol of the messaging system.

Migrating to a Different Object Management Type

You can use In Memory object management in early phases of development. In later phases, you can implement Cache or Store OM and take advantage of features it makes possible. Perform tests after changing object management type.

As with any change in configuration, be sure to perform thorough testing before going into production.

Summary of Object Management Features

The following table illustrates features supported for each OM type.

OM Type Persistence Data Recovery Partitioning Clustering Fault Tolerance
In Memory No No No No No (use Cache with Memory Only objects)
Cache Yes Yes Yes Yes Yes (at agent level)
Store Yes Yes Yes Yes Yes