The scenarios that are implemented by the application are described in the section called “Scenario”. This section explains in more technical terms what happens at runtime given a debit that triggers the fraud detection rules. (You will learn more details about the terms shown in italics below, as you complete the tutorial steps):
A message arriving through a TIBCO BusinessEvents® Extreme channel is transformed into an event. (At design time you create an event type for this purpose, with the appropriate properties.) The event instance is then asserted into the Rete network, an in-memory network of objects based on the Rete algorithm, which enables fast matching of facts with rule dependencies.
The presence of this new event in the Rete network causes the inference engine to check for rules that are designed to be triggered when this event is asserted.
A rule that is triggered by this event executes. A rule might make changes to concept instances, create an event and send it to a channel (and out of the TIBCO BusinessEvents® Extreme application to some destination), and so on. The rule then consumes the event unless there is a reason to persist the event.
![[Tip]](images/tip.png) | |
Event lifespan It is important to consume events when they are no longer needed so that they do not trigger rules to fire erroneously. On the other hand, it is also important to use a long enough time-to-live (TTL) setting for an event, so that it exists long enough to perform all work needed, for example, to trigger rules that correlate multiple events and take appropriate actions. |