Modeling the Concepts of Events

BusinessEvents lets users build UML-based models for describing applications, services and servers on which those applications and services are deployed. These models describe the causal and of time relationships between possessions. By employing these models, the software can recognize exceptional patterns, likely impacts and predictable outcomes. For example, the concept model below describes causal dealings between event sources

Modeling and organization the States of Events

   A UML-based “state model” describes how applications and services cooperate as part of actions and processes.

•Used for describing tasks, sequences of tasks (processes), and probable outcomes or “states” of tasks and processes.

•A state machine captures and stores in an in-memory database the status of events relative to causes, roles and probable behavior for instant connection against additional events. Data can continue for any length of time depending on how long an event is relevant. The example below shows a state model for processing an order.

 

Application of Rules

   The key to winning CEP is defining and applying rules that say the flow of information and responses as events play out in the situation of the conceptual and state models described above.

•Rules editor lets IT staff define static and dynamic dealings among events within their project and across their extended value chain.

•Users can specify the event or chain of events they want to check, the condition at which a exacting event is important and the action to be taken when the situation is met.

•Rules can filter, associate and total events by applying constraints and threshold limits.

•Rules engine is based on industry-standard RETE protocol for knowledge and stability, but has been recompiled and tuned to support immediate application of thousands of rules to millions of events.

Flexible Event Capture Service 

   BusinessEvents leverages TIBCO’s inheritance of leadership and know-how in developing software that supports event-driven structural design, a requirement for real-time business.

•Can imprison and process events being routed across TIBCO’s own integration and messaging infrastructure: TIBCO BusinessWorks, TIBCO Enterprise Message Service, TIBCO tryst.

•Can capture and process events from within other vendors’ implementations of JMS, and other integration platforms including IBM’s MQSeries messaging software.

•Organizations can implement BusinessEvents in a non-invasive “layer and learn” mode to start measuring operational performance without defining models or varying the way users interact with applications.