TIBCO BusinessEvents® Architect's Guide
Software Release 5.3
May 2016
- Important Information
- TIBCO Documentation and Support Services
- Complex Event Processing (CEP)
Complex Event Processing (CEP) is a set of technologies that allows events to be processed on a continuous basis. - Channels Destinations and Events
Channels (except for local channels) represent physical connections to a resource, such as a Rendezvous daemon, JMS server, HTTP server or client, Hawk domain, StreamBase server, or a metaspace in TIBCO ActiveSpaces. - Concepts
Concept types are descriptive entities similar to the object-oriented concept of a class. - Rules
Most rules in TIBCO BusinessEvents are used for inferencing. However, regular business rules also have a role to play. - Runtime Inferencing Behavior
At runtime, one or more nodes (JVMs) running one or more TIBCO BusinessEvents inference agents process the incoming events using a Rete network as the inferencing engine, and a set of rules that are triggered by conditions in incoming events. One or more event stream processing query agents can query incoming events. - Object Management (OM)
Object management refers to various ways that TIBCO BusinessEvents can manage the ontology object instances created by TIBCO BusinessEvents. - Distributed Cache OM
Cache object management (OM) is the standard choice for most TIBCO BusinessEvents Cache Object Management Feature Overview. - Cache Modes and Project Design
The Rete network consumes a large amount of the available memory in the JVM. - Concurrency and Project Design
You can use multiple concurrently active inference agents to achieve load balancing, scaling, and performance. - Threading Models and Tuning
Event preprocessing is multithreaded, and for each destination you need to choose a threading option: Shared Queue, Destination Queue, or the Caller’s Thread. - Glossary
Copyright © TIBCO Software Inc. All rights reserved.