Skip to main content

TIBCO BusinessEvents 5.x : Understanding CEP and Getting Started

Complex Event Processing (CEP) is a set of technologies that allows events to be processed on a continuous basis. TIBCO offers a complete platform to enable CEP that is, TIBCO BusinessEvents. It is a Rule Engine where Event-Based Programming Paradigm is followed that has Java at its core.

CEP is unlike conventional event processing technologies, however, in that it treats all events as potentially significant and records them asynchronously.

CEP Applications are event-driven in nature, therefore some of its aspect has real-time behavior. For example, “Situation Awareness,” “Sense and Respond,” or “Track and Trace” are some of the aspects that CEP application can have that overlap in actual business situations.

Learning TIBCO BusinessEvents (BE) for developing such CEP Solution can open up the world of Even Processing for developers. TIBCO BusinessEvents Rule Engine's working can't be understand without understanding what "Run to Completion" Cycle is all about. Also before understanding CEP and developing solutions, one must have a strong foundation of programming language and problem solving with rock solid basic understanding of the principles of Object Oriented Programming.

 To understand more effectively, you can imagine the BE Engine as a child who is taught to understand, identify and react according to varies situations put forward. For example if you have to teach the baby, "Pull your hands off when there is hot metal near by".  How would you do that? Following can be the sample process in order to teach the baby this skill.
  1. Tell the baby, What is "Hot Metal"?
  2. Tell the baby, How to "Pull Your Hands off"?
  3. Tell the baby, When to "Pull Your Hands Off"?
Well, that's all you need to teach (actually it is defining) to BE Engine as well.
  1. Defining the "Hot Metal" to the BE Engine by identifying the properties of the object like temperature, texture, shape, size, material, etc.  and saving as "Concepts".
  2. Defining the procedure to "Pull Your Hands Off" as reactive Action to be performed when hot Metal is detected. This will be your "Rule Action".
  3. Define the condition and relate it with action "Pull Your Hands Off". This will be your detection point as an "Event".
But that's not it, we can always explore more and learn beyond these basics. For example, In TIBCO BusinessEvents, we have to define a Medium (i.e. Destination and Channel) in order to wait and listen for the Event. Now, as a beginner, it is pretty much easy to understand, what is a CEP and how well it is connected with the reality. I hope it will help you getting started for designing a CEP Solution.

Similarly, we can break the data flow architecture of any CEP Application and correspondingly trying to develop the understanding of the Objects, Actions, and Relations involved in CEP.

Leave the comments below if it helps or if there is any question. I would be happy to help you all.
Thank You Guys, See you later. Till then, Good Luck. and Have a great CEP Exploration.

Please do like, share and subscribe. This would help me grow my blog.

- Vijay Prakash Tiwari

Comments

Post a Comment

Popular posts from this blog

Art of Observation: Introduction

Since Ancient times, Observation has been a fundamental behavior that is being practiced by most of the living creatures. It has also been one of the secret ingredients in evolution for many Species. Due to Humans' strong observatory skills, we find ourselves on the peak of the ladder of evolution. Therefore, the majority of the time, we observe things around unconsciously as just another natural behavior. Power of Observation is so vague and wide that if one can understand it, learn it, control it, and practice it, then for that individual, winning the battle for success is certain. Observation has been the primary source of success for every example we see around. For Example, all innovations and discoveries in science and technology and cultural practices are resultant of observation. It has been a central key activity in Historical, Economical, and Political belief system. If we say, necessity is the mother of all discoveries, then we should also understand that observati
2 comments
Read more

TIBCO BusinessEvents 5.x : Run to Completion (RTC) Cycle and Conflict Resolution Cycle (CRC)

TIBCO BusinessEvents (BE) utilizes, Run to Completion Cycle (RTC Cycle) and Conflict Resolution Cycle (CRC). RTC and CRC do play very significant role in designing the Complex Event Processing (CEP) Solution while using TIBCO BusinessEvents as a developing tool. Therefore it is very much important to learn about the RTC Cycle and CRC Cycle. RTC and CRC utilizes a runtime environment, Rete Network, to hold all the rules, triggers and relationships. Rete Network is based on  Rete Algorithm  therefore it provides the basic property of Inference to the RTC in TIBCO BusinessEvents Engine. Here, one very important property of RTC and CRC to understand is that, " CRC is initiated wherever there is any change in Rete Network cause by external actions when the change is asserted to the Working Memory of the Engine, after which an RTC is initiated. RTC ends when Rule Agenda is Empty or no other rule action needed to be executed. This is called Inferencing or Forward Chaining. One RT
1 comment
Read more