TIBCO BusinessEvents

TIBCO BusinessEvents

Score 7.7 out of 10
TIBCO BusinessEvents

Overview

What is TIBCO BusinessEvents?

TIBCO BusinessEvents® allows organizations to quickly build event-driven rules systems that intelligently process streams of events at the speed they are generated - supporting realtime decision making, automation, and proactive responses.
Read more

Recent Reviews

BE is a must!

8 out of 10
September 05, 2018
We use BE across our entire enterprise and it ensures our quick delivery of complex business ventures and new business intiatives.
Continue reading
Read all reviews

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of TIBCO BusinessEvents, and make your voice heard!

Return to navigation

Product Details

What is TIBCO BusinessEvents?

TIBCO BusinessEvents® allows organizations to quickly build event-driven rules systems that intelligently process streams of events at the speed they are generated - supporting realtime decision making, automation, and proactive responses.

TIBCO BusinessEvents Features

  • Supported: Enterprise Capable and Proven
  • Supported: Rapid Application Development
  • Supported: Empowering Business Users & Data Analysts

TIBCO BusinessEvents Videos

Enrich Your Enterprise with TIBCO Streaming Analytics
Enrich Your Enterprise with TIBCO Streaming Analytics

TIBCO BusinessEvents Integrations

TIBCO BusinessEvents Competitors

TIBCO BusinessEvents Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo
Supported CountriesWorldwide
Supported LanguagesArabic, German, French, Italian, Korean, Simplified Chinese
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

 (49)

Reviews

(1-13 of 13)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Our company has a long history of using the TIBCO family product, previously we majorly used the TIBCO BusinessWorks to build the data flowing and adaptation back-end process, together with the TIBCO EMS. In recent years, together with the TIBCO ActiveSpace, TIBCO BusinessEvents has been introduced into the IT department, aiming to further strengthen our efforts to leverage the "event-driven" architecture to better support our increasing real-time business decision making demand due to business expansion. TIBCO BusinessEvents has become the core technology stack of our company's Enterprise Foundation Service
  • It allows us to build rule-based model-driven application, to collect, filter, analyze, correlate various business events in our real-time event flow
  • It makes various business applications/components easy to integrate (loosely decoupled but chained via the events flow) together
  • Its distributed rule engine and embedded in-memory data grid (ActiveSpace) gives us a lot of flexibility and room to play with a large amount of rules and data with high performance
  • Due to some technical limitation of the embedded ActiveSpace, when the application is deployed in the multiple data-centers with distance, the data/event sharing across the data centers become very challenging
  • More machine learning and deep learning features could be added to help business further use the real-time event flow more efficiently, to support the pattern recognition and condition self-learning mechanism
  • More focus could be added to better integrate with public major cloud services
BusinessEvents is not very well suited for Cloud native solutions, but it is suitable for traditional enterprise self-maintained data center deployment. And it gives the business the power to define/modify/update the business rules, in a visualized way, instead of asking IT team to maintain them. Generally speaking it is a very comprehensive rule engine solution, but not suitable for "hook on" some other complex computation/data processing logic
  • Online training
  • Self-taught
Kick-off training is very helpful to quickly build prototype, while self-learning is very good for developer to gradually master the platform
September 05, 2018

BE is a must!

Score 8 out of 10
Vetted Review
Verified User
We use BE across our entire enterprise and it ensures our quick delivery of complex business ventures and new business intiatives.
  • Business driven interactions with our enrollment engine.
  • BE and BW usage need to be clearly defined and lines drawn
BE is great for translating business rules to intelligent actions systematically.
  • In-person training
On site training is a must have if you don’t have experience!
Paolo Avalle | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
It is used across the whole organization addressing problems spanning from R&D to financial analysis.
  • Dashboard for real-time analysis
  • R-scripting, although the R editor could be improved, there are syntax inconsistencies between R-studio and R-opensource in TSSS
  • Basic statistics and drill down capabilities
  • Better integration with R versions and better debug for R-scripts in Spotfire. There are inconsistencies in syntactic expressions accepted by R-studio and not accepted in Spotfire. Accelerating the debug would be awesome. Having a command like View (data frame) that directly output in the dashboard would be a great accelerator.

Standard dashboard for basic statistics. GREAT

Advanced multivariate modeling needs to be coded in R for example, LESS GREAT. You would get a million users for off-the-shelf multivariate modeling like SIMCA.

The integration with Statistica is a great idea but much of its success will depend on the speed and the ergonomics by which you integrate the development workflow for multivariate models PLS/PLS-DA/ PCA etc.

You should implement some of the features offered by SIMCA (Sartorius Stedim) and expand the multivariate analysis offering and more advanced tools (from Random Forest to T-SNE and machine learning / AI). You will get lots of 'love' from pharmaceutical engineers. :)

  • Self-taught
Score 7 out of 10
Vetted Review
Verified User
TIBCO BusinessEvents (BE) is used in multiple business applications as well as gateway implementations at Western Union. It is used to receive, transform and handle events/transactions in real-time. Business users are provided with the capability of making and changing rules dynamically using BE based applications. Since every transaction in the company deals directly with funds every application plays a critical role.
  • Business users have the capability of changing rules dynamically without downtime in the application.
  • Real-time processing capability decreases latency and increases the efficiency of the features developed in TIBCO BE.
  • Capability of caching the data as well as managing it as an independent entity as TIBCO Active Spaces is a huge addition.
  • TIBCO BusinessEvents Studio for altering the decision tables/rules can be made more robust and production ready.
  • TIBCO BusinessEvents views can be made more robust. This will avoid additional BI layers on top of the data.
  • Event Stream Processing and Pattern Matching add-on of TIBCO BE is an awesome feature. It can be made more robust by implementing machine learning and deep learning.
  • Real-time processing.
  • Event Streaming.
  • In-memory computing.
  • Dynamic rules.
  • BRMS.
  • Self-taught
I learned BE in 2011 by myself. It took time for me to understand the point of view of a Complex Event Processing application, but soon I started relating and analyzing the problems in real world that can be effectively and efficiently solved using TIBCO BE as a CEP solution. Having learnt the application from scratch, I was able to train and help a number of my colleagues.
Score 4 out of 10
Vetted Review
Verified User
We Use Business Events Rule Engine in regards with Fraud Detection use cases. Various rules built and deployed to identify fraud across different channels. We use Web Studio to author most of the rules that are executed by BE Engine. ActiveSpaces used as a caching mechanism between BE and Backing Store.
  • Optimized Rules engine
  • Extremely efficient decision tables
  • Web based rules authoring tools
  • Not so easy hot deployment
  • Web Based tool lacks some features needed in Rules Authoring
  • Does not work well with public cloud vendors, e.g. not easy way to run BE and AS with ECS on Amazon Web Services
Business Events is well suited for medium to complex use cases involving complex event processing. BE is useful in areas where Buisness Owners want to actually implement business rules defined by designers/developers. BE is well suited where Busieness Rules/ Thresholds change frequently; BE's hot deployment capabilities can be utilized for such scenarios. BE is very well suited for on premise deployments.

BE is not very well suited for Cloud native solutions. Specifically when it uses embedded ActiveSpaces as in memory cache.

  • Self-taught
Most of the staff was able to train themselves using tibco BE.
Score 7 out of 10
Vetted Review
Verified User

BusinessEvents is used in my organisation to deliver a capability of rules-driven processing on the events that are flowing through the middleware layer. The requirements expect TIBCO BusinessEvents to process states of various electrical devices, perform actions based on the changes of a state exceeding a defined threshold of level, time, or value increment or just of a count as the event. The following business problems are being addressed by using BusinessEvents: event monitoring, event correlation, event recording and event filtering where an event may be observed as a change of state with any physical or logical or otherwise discriminated condition. Preserving the state of an object is achieved through State Machine.

  • Process network events and use defined rules to infer system occurrences
  • Monitor distribution substation switches that have remote telemetry to infer the actual switch state
  • Perform rule based Network Alarm suppression
  • Ability to handle/process huge real time data
  • Faster processing of data with high rate of performance.
  • User-friendly setup and quick event formulation capabilities
Well suited in scenarios where the business landscape has several probabilities of data that needs to be processed by ruke driven approach.

No suited for very huge volumens of data processing.
  • Online training
  • Self-taught
Helped in understanding intricate business flows, provide design and implementation specific improvements and support the applications and resolve issues as and when arised.
Fabio Martone | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
In the actual project, TIBCO BusinessEvents is being used as correlation engines. Its purpose is to collect metadata about service requests and responses across the Service Backbone, correlate them, and provide statistical information about deployed services, such as the number of hits for each service operation, successes and faults, average latency, and so on. All these information are then delivered to another component to be persisted and then read from a GUI. Thanks to this statistical information about the deployed services, the user would be able to figure out the health of the system, create business monitoring rules, and act immediately whenever unexpected patterns appear.
  • One of the simplest use of TIBCO BusinessEvents, is for "Condition Detection" scope. Let's assume we like to monitor business services or our corporation, and create monitoring alerts whenever certain conditions are reached. For example, a monitoring rule could be: "when a service call receives more than 80% of fault responses within a minute, generate an alert (send an email)".
  • In this scenario, TIBCO BusinessEvents offers a very powerful rule engine. In the rule engine will be defined all the monitoring rules, and their threshold. The rule engine will receive events with statistics information about service calls, eventually correlates and aggregates those message, and when particular condition are detected by the defined rules, an alert is generated
  • One interesting capability of TIBCO BusinessEvents, is to recognize situation. One example over all, could help to understand the "Situation Recognition" scenario: the Bank Fraud detection.
  • Let's assume a bank would like to define a solution to identify when a credit card fraud is in act. Now, a simple use of the credit card by its owner, most probably, is not a fraud. So the system should avoid to raise alert every time. But the system should be able to recognize certain suspicious conditions, as for example when the credit card has been used for purchase in a shop in Italy, and after a pair of hours in one store in USA.
  • This means that one single event (usage in Italy) is not enough to define the fraud, but the system is able to keep the event, and process it once others events arrive, in order to recognize suspicious situation.
  • One particular pattern, where TIBCO BusinessEvents would be very helpful, is for Track and Trace patterns.
  • Let's consider an aviation company, that needs a process to follow customer's baggage. The customer drops off his baggage at airport, a bar code is assigned to it, that belongs to the owner. The baggage should follow a route to reach the target airplane, be loaded on the airplane, once arrived at destination unloaded and sent to the correct belt to be collected by its owner.
  • All the steps above, con be modeled with a state machine, where the baggage change its state at each passage under a bar code reader for example.
  • This solution would allow companies to track baggage from the beginning (when customer drops the baggage at counter) to the end (customer collects his baggage at destination), and establish any problem during the path.
  • TIBCO BusinessEvents offers really several features, many way to customize and adapt it to own requirements. One interesting feature is the opportunity to create Rules, at runtime, by an user that is not developer, using rule templates.
  • This feature, well implemented and with few interesting addon, has an architecture not very simple.
  • For example, we have a Business Monitoring component, where the business user can define his monitoring rules, the rules are persisted on DB, and picked up at any time by another component.
  • The component that reads the rules from the DB is not a rule engine, this means that is not performing very well for this scope, and also it needs each time to retrieve the rule to execute from the Database.
  • Our intention is to substitute this last component with TIBCO BusinessEvents, in order to use the power of the rule engine. But, to create the rules, there is a new mechanism, that should be integrated with the existing GUI, and more else, the rules are persisted on file system.
  • There is no way for the developer to auto create the rules internally, and enable them in the working memory, for example generate the rules from entries on a database, and create the rules directly in the working memory.
  • The existing solution injects the new rules in the working memory from outside.
TIBCO BusinessEvents is part of the CEP (Complex Event Processing) family, this means that it fits perfectly in all those scenarios where a correlation between incoming events is required. Where a stateful process is necessary. It does not fit well for a kind of Process Orchestrator scope, where simple events are coming in, and there is a well-defined behavior the system, would have on incoming request, and no particular reason to use a rule engine and its complexity. Anyway, there are particular cases where BusinessEvents would be a good actor in orchestrating a portion of CEP solutions activities
  • Self-taught
Learning the product on the job, by myself, helped me to enter immediately into the real utilization of the product, with real cases and scenarios, where usually during a training only ideal cases are used.
One of the hardest part of TIBCO BusinessEvents understanding, is determine the boundaries of utilization, when it is really useful and increase performances, and when it is redundant, and other products can do better. And without being projected into real utilization, could be harder, after the normal training, to understand this part.
January 18, 2018

TIBCO BE Product Review

Score 5 out of 10
Vetted Review
Verified User
Currently, Fraud department in my company uses Business Events, to run rules to detect fraud based on certain data points and internal calculations. We heavily use BRMS functionality to dynamically create and deploy rules on ad-hoc bases.
  • BE does inferencing part very well
  • Correlate a lot of data streams and make decisions on very minute scales.
  • BRMS functionality with hot deployment should be improved a lot
  • As everyone is moving towards cloud, BE should easy have docker support and should be able to move dockers easily to cloud env.
Business Events is well suited for the scenario where you want to use the product just as a rule engine instead of making a lot of other heavy calculations inside business events engine.
  • Self-taught
Not much impacts as training provided by tibco is very basic.
.john omahen | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
It replaces the current legacy fraud operational system. We incorporated a number of producers of real-time events (e.g. web UI claims process and RSA Web Threat Detection). TIBCO BusinessEvents (BE) is the consumer that runs a set of rules against those events to determine the next steps in the claims process.
  • Great event driven engine with a rich event model
  • Provides ability to use Web Studio to generate basic rules that will drive the outcomes
  • Allows for Java implementations of other rule sets
  • Has in-memory caching abilities
  • We had to write our own business rules interface that matched how our previous systems operated. Web Studio has gone through some great changes but in that time we have made a decision to move to Kafka, Kinesis, and Spark for our events streaming solution in AWS.
  • We did not modify our business process flow to take advantage of BE. If you are not truly running an adaptive business process effort, then BE could be overkill.
If you are truly event driven and are willing to implement an adaptive business process then BE is great. The challenge is involving the business and ensuring they are in charge of the product release. In our organization, when the business drove the product releases (which included BE applications) then BE was a winner. When developers took over and had no real event-driven background then all the calls were synchronous which is a killer to the event-driven process.
  • Online training
  • In-person training
  • Self-taught
We had great BE support from TIBCO. Since I had been around BE since the earlier years at TIBCO I put together a local training effort to ensure each of our original developers could build the basic patterns (e.g. from Paul Brown's book on Architecting Complex-Event Processing Solutions with TIBCO).
November 14, 2017

BE isn't really worth it

Score 2 out of 10
Vetted Review
Verified User
Tibco BusinessEvents is being used by several groups across the company in non-legacy projects. It was supposed to be the business rules engine that would drive the event-driven, real time capabilities the company wanted. The in-memory rules engine was supposed to enable instant decision making over the life of the product.
  • The rules engine works well for simple rule sets in smaller batches
  • TIBCO consultants are usually very good with the product
  • The product does not scale well as a central manager of rules.
  • It can be difficult to deploy and scale without extensive knowledge of a lot of inner workings of the product, which is not widely available.
  • It is a very heavyweight product, requiring lots of resources with little visibility as to how resources are being utilized.
  • The BE language resembles Java, but is just different enough to have a learning curve and cause issues if one is unfamiliar with it. Plus it is not nearly as flexible as Java.
It is very poorly suited to run a central rules engine for large numbers of transactions. Perhaps as an input-output rules engine it might be ok, but as far as managing those events itself it does a poor, overly complex job.
  • Self-taught
The online resources for training are very poor, almost requiring you pay for training. Most learning was done peer to peer as in-person training was prohibitively expensive for an already expensive product.
November 06, 2017

A real Fast Data Engine!

Score 6 out of 10
Vetted Review
Verified User
For enrollment validations, we used:

  • BusinessEvents (BE) was acting as a rules engine to perform some initial set of validations, transformations, computations, and also acting as a control flow management engine.
  • We used BE's state diagram to specify what process or rules to apply and behavior was specified as declarative rules.
  • It does not require major implementation effort to address major business issues.
  • Works well as a rules engine with process orchestration capability.
  • Focused on handling only light weight, ad-hoc processes.
  • The designer should be more easy to use (like TIBCO BW).
BusinessEvents is very useful in all scenarios where there is a need to respond quickly to events.
  • Self-taught
Score 7 out of 10
Vetted Review
Verified User
TIBCO BusinessEvents has been used to implement the business catalog engine of the business catalog. BE was used by the IT department. come detto prima è stato usato per realizzare il BRE di un Nuovo Catalogo Commerciale
  • It does not require major implementation effort to address major business issues.
  • It is quite efficient even if subjected to high stress.
  • Is extremely versatile
  • It should also allow TIBCO BW to make more use of drag and drop configurations
BE is very useful in all scenarios where there is a need to respond quickly to events. For example, a request that needs to be accomplished requires enrichment from other sources
Score 6 out of 10
Vetted Review
Verified User
For enrollment validations, we used:
  • TIBCO Business Events (BE) as the container, delegating to TIBCO BusinessWorks for interfaces to existing systems/extracting data as required for event processing.
  • BE was acting as a rules engine to perform some initial set of validations, transformations, computations, and also acting as s control flow management engine.
  • We used BE's state diagram to specify what process or rules to apply and behavior was specified as declarative rules.
  • Works well as a rules engine with process orchestration capability.
  • Maintains the state as the process goes through various stages.
  • Well defined state diagram that specifies what process or rules to apply and behavior is specified as declarative rules.
  • Needs a more user friendly interface to modify business rules.
  • Focused on handling only light weight, ad-hoc processes.
  • Not a rapid application development tool. Most of the time developers end up writing Java code.
  • Best suited for collecting data from various sources, understanding the meaning of this data and its context and identifying and acting on a critical business moment for mostly light weight, ad hoc business processes.
  • Not the best choice where business rules are constantly changing/will require a lot of maintenance post production or where business users need to maintain rules.
Return to navigation