A prioritized list of rule actions that may execute. Also known as the rule agenda. TIBCO BusinessEvents recreates the agenda each time a change in the Rete network requires rules to be re-evaluated, for example, when a simple event is asserted. A rule action in an agenda may disappear without firing when the agenda is recreated, because conditions are no longer met.
Put facts into the Rete network. When object instances or events are asserted into the Rete network, rules may fire as a result. See also
fact,
retract.
A disk-based database to provide persistence and a better level of reliability for cache objects.
In TIBCO BusinessEvents, a type of object management. Generally refers to distributed storage of facts (objects) in memory. See also
object management (OM),
cache mode.
A group of processing units each running one or more agents configured for use by the cache-based object management type. Some agents are generally configured as cache agents. They store cache data for use by other cluster members. See
object management (OM),
cache.
Various cache mode options are available at the object level, for use with cache-based object management. They enable you to tune the performance of your application, and reduce its footprint in memory. See also
object management (OM),
cache only,
cache plus memory,
memory only (local only).
A processing unit configured with a non-reasoning agent used as a storage node only. Used with Cache object management. See also
agent,
cache.
One of the cache modes, used at the object level. Instances of entity types that use cache only are serialized and kept in the cache until needed. They must be explicitly loaded into the Rete network when needed for rule processing. See also
object management (OM),
cache,
cache mode
One of the cache modes, used at the object level. Instances of entity types that use cache plus memory are serialized and kept in cache until needed. Used for objects that change infrequently. See also
object management (OM),
cache,
cache mode.
A named configuration that allows TIBCO BusinessEvents to listen to a stream of events from a given type of source, for example, JMS messages. A channel contains one or more destinations. See also
destination.
As used in persistence object management, a checkpoint is the point in time at which working memory data is written to disk. The term checkpoint also encompasses all the activities involved in writing the data to disk.
XML file containing properties to define the cluster, processing units, and agent classes. Configuration done using TRA file properties in earlier releases is now done using the CDD editor in TIBCO BusinessEvents Studio.
Example: A complex event might result from the following simple events that all occurred within one week’s time: A stock broker buys shares of xyz stock. The same broker submits a very large order for xyz stock on behalf of a customer. The same broker sells shares of xyz stock at a profit.
Correlation of multiple events from an event cloud, with the aim of identifying meaningful events and taking appropriate action.
An abstract entity similar to the object-oriented concept of a class. A concept is a description of a set of properties that, when grouped together, create a meaningful unit. Concepts can be organized in a hierarchical structure.
Example: Department, employee,
purchase order, and
inventory item are all concepts. The term
concept type refers to the definition and the term
concept instance refers to the actual object. Concepts are generally created using event data. See also
event.
A property within one concept that references the ID of another concept, known as the referenced concept. A type of relationship between concepts.
A cycle of activities during which the engine executes one set of rule actions on the currently asserted facts. One RTC may contain multiple conflict resolution cycles. See also
Run to completion (RTC) cycle,
agenda.
A concept that exists entirely within another concept. A type of relationship between concepts.
You can add Java-based custom functions as needed to supplement the library of standard functions provided with TIBCO BusinessEvents. See also
ontology function,
rule function,
standard function.
A tabular form presenting a set of conditions and their corresponding actions. A graphical tool for building rules. Used in TIBCO BusinessEvents Decision Manager.
A class that performs conversion tasks. In TIBCO BusinessEvents, a deserializer converts messages to events. See also
serializer
A channel property that defines a contact point on a given channel. For example, for a TIBCO Rendezvous channel, the destination properties would specify the subjects on which to listen.
In TIBCO BusinessEvents, a form of cache-based object management. In a distributed cache, cached object data is partitioned between the processing units (JVMs) in the cache cluster for efficient use of memory. See also
object management (OM),
cache.
A concept, simple event, or scorecard. Entity types are the definition of the entity. Similar in meaning to object. The term "instance" generally refers to a concept instance.
To remove an object or entry from a cache. An eviction policy defines when an object is removed from the cache. See also
object management (OM).
At the end of the event’s time to live period, the event is said to expire. It is removed from the Rete network and (as needed) acknowledged. Other actions depend on the type of object management used. See also
time to live.
In TIBCO BusinessEvents, a form of object management. Refers to storage of facts (objects) used by the runtime engine in JVM memory. See also
object management (OM).
One of the cache modes, available for cache-based object management configuration. Instances of entity types that use this mode are not stored in cache or backing store and are available only in the processing unit’s local JVM memory. See also
object management (OM),
cache,
cache mode.
In a deployed system, inference agents process incoming events using a Rete network and a set of rules that are triggered by conditions in incoming events. Inference agents in Cache OM systems allow fault tolerance and load balancing. See also
Rete algorithm.
Similar to the Java term "object instance." By custom, applied only to concepts, though event definitions have object instances also.
The aspect of TIBCO BusinessEvents that deals with management of all the facts used in the runtime engine. Often shortened to OM in documentation. See also
in memory,
cache,
persistence.
TIBCO BusinessEvents generates ontology functions for each entity type in a project. There are three types of ontology functions:
constructors, to create a simple event or concept instance;
time events, to create and schedule time events, and
rule functions, to invoke rule functions. See also
custom function,
rule function,
standard function.
Similar to a JMS message, a simple event can contain properties and a payload. The payload holds the content of the message. You can define the XML schema for the payload when you configure the simple event definition. Payloads can also contain strings and Byte arrays.
In TIBCO BusinessEvents, a form of object management. Refers to storage of facts (objects) used by the runtime engine, in a database. See also
object management (OM).
Definition of a TIBCO BusinessEvents engine which runs in one JVM. Contains agents and other properties.
A query agent is a non-reasoning agent that and has read-only access to the underlying objects in the cache cluster. A query agent has no Rete network. Available only with TIBCO BusinessEvents Event Stream Processing add-on software. See also
agent.
An in-memory network of objects based on the Rete algorithm which enables fast matching of facts with rule dependencies. "A Rete-based expert system builds a network of nodes, where each node (except the root) corresponds to a pattern occurring in the left-hand-side (the condition part) of a rule. The path from the root node to a leaf node defines a complete rule left-hand-side. Each node has a memory of facts which satisfy that pattern." (
http://en.wikipedia.org/wiki/Rete_algorithm)
Rules Management Server. The server component of TIBCO BusinessEvents Decision Manager add-on software. RMS manages the rules management repository.
A run to completion (RTC), cycle generally begins when an external action causes changes to the Rete network. It ends when there are no more rule actions to execute as a result of that initial change (and any subsequent changes caused by rule actions). One RTC is composed of one or more
conflict resolution cycles. Other terms for RTC are
forward chaining and
inferencing. See also
conflict resolution cycle.
A declaration, with a set of conditions and actions. If all the conditions in the rule are satisfied by facts in the Rete network (and the rule is at the top of the agenda), TIBCO BusinessEvents executes the action. See also
working memory,
Rete network,
agenda.
A class that performs conversion tasks. In TIBCO BusinessEvents, a serializer converts events to messages. See also
deserializer
An object representing a business activity that happened at a single point in time. A simple event includes information for evaluation by rules, metadata that provides context, and a separate payload — a set of data relevant to the activity. See also
advisory event,
event,
simple event definition,
time event,
time to live,
expires (event).
A description of the channel, destination, properties, and payload for a simple event. See also
simple event.
A language that assists in building a diagram of any complex entity. TIBCO BusinessEvents diagrams use the UML. The TIBCO BusinessEvents term,
concept, is similar to a UML class.
A rule function whose signature is defined in a TIBCO BusinessEvents project and whose implementation is defined using decision tables. For use by TIBCO BusinessEvents Decision Manager add-on software. See also
rule function.
The runtime processing area for rules, objects, and actions. Rules apply only to data in the working memory. Often used to mean Rete network. See also
rule session,
Rete network