TrustRadius
https://dudodiprj2sv7.cloudfront.net/product-logos/eB/zK/6L33UM6D14VA.pngTIBCO Spofire review.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.,10,Self-taught,Positive: dashboard is very informative and extremely powerful Negative: we need to have more capability for data integration - OR for prototyping data integration and analytics, without resorting to something complex and big like StreamBase (which is truly amazing) but requires too much specific knowledge for industrial application. something easier to learn would be great. for example, I was able to learn KNIME and prototype a solution in a week. But StreamBase is too complex.,We use Spotfire in many different remits from R&D to manufacturing with tangible benefits.,I love the capability of handling data with properties/scripting/and filtering. I use these to calculate expression in many different dashboards.,I use Spotfire to build advanced visualization dashboards based on multivariate analysis scripted in R.TIBCO BusinessEvents as CEP solution for complex problemsIn 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.,9,Self-taught,TIBCO BusinessEvents, whenever it was used consciously, gave a big improvement to the projects, solving complex problem not easily solved otherwise. Same solutions, realized in technologies as Java or TIBCO BusinessWorks, could require an effort of 40% more in terms of time or realization, compared with a BusinessEvents. And in terms of performance, we have had a comparison of a solution where monitoring rules had to be executed, developed with BusinessWorks and BusinessEvents. The BusinessEvents showed a capacity to perform up to 15x time faster, with the same load work,The decision-making capability has not been used in our organization,TIBCO BusinessEvents was used with success to handle a solution involving complex use cases and several rules. It was used for a order gateway component, where, in a Telco company, all incoming orders had to be validated, respecting a combinations of conditions, defined in several rules. If the order passes successfully the validation, then the order could be sent to an orchestrator component for its execution. Otherwise the order gateway rejects it immediately,No real use of this portfolio at moment,DroolsHow to get the business to adapt to changeIt 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.,7,Online training In-person training Self-taught,We are able to stay on top of major threats to our claims process We have been able to at least help the business understand what an adaptive business process can do for them,Yes we have used BE to ensure the ability to track and react to threats across the organization.,Yes since we have been able to build rules now in smaller components. This has allowed the business team to ensure flexibility as we apply similar rules to various clients in various markets.,We have used other tools for analytics and visualization.,Business Events, the prodigy of TIBCO!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.,7,Self-taught,Positive : Real-time event stream processing helps handle transactions very efficiently. Negative : Earlier versions of BE (5.0 & 5.1) had major issues in data handling in cache that impacted the data integrity of the application. Positive : Decision Tables are a huge plus in TIBCO BE.,Both my current as well as previous organizations benefited from TIBCO BE based applications. Money Transfer: Decreased latency in real-time money transfer by the company. Retail: Helped in implementing an omnichannel application that supports stores, web and call center traffic. CPG: Real-time tracking application that was first built to monitor trade and then used the data to recommend [solutions].,In the use case of integrating the entire company with multiple vendors who differ with one another by a plethora of features such as rules, SLA, TOC, data contracts, data agreements, TIBCO BE's features of BRMS & event handling capabilities made a mammoth and complex application look simple and easily manageable.,Yes.The BRMS feature of TIBCO BE has provided the business team with a huge advantage. The humongous data store persisted in BE making analytics simple by being a one-stop app for the data.,Drools and CassandraTIBCO BusinessEvents ReviewWe 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,4,Self-taught,BE is well suited for our on-prem fraud detection capabilities Total ecosystem around BE makes the implementation expensive. such as EMS, Admin, HAWK etc.,We have multiple products from TIBCO such as BusienssWorks, EMS, BusinessEvents , ActiceSpaces etc. It makes sense to use CEP from TIBCO as it works really well with other tibco complonents. But dependency on other TIBCO products makes implementation expensive. There is no much help available to make these product run very well on public cloud infrastructure,There is no doubt about BE's capability to handle complex business rules at scale. We are not aware of any other product that can manage business rules as efficiently as TIBCO BusinessEvents. Multiple channels and transports make it uniquely positioned to build complex systems implementing business rules.,We use BE along with other products such as BusinessWorks, ActiveSpaces and EMS. We never had issues with this type of integrations. BusinessEvents was never explored for analytics and visualization capabilities.,
Windows, Linux, Mac
TIBCO BusinessEvents
32 Ratings
Score 7.7 out of 101
TRScore

TIBCO BusinessEvents Reviews

TIBCO BusinessEvents
32 Ratings
Score 7.7 out of 101
Show Filters 
Hide Filters 
Filter 32 vetted TIBCO BusinessEvents reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-11 of 11)
  Vendors can't alter or remove reviews. Here's why.
May 09, 2018

TIBCO BusinessEvents: "TIBCO Spofire review."

Score 10 out of 10
Vetted Review
Verified User
Review Source
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. :)

Read Paolo Avalle's full review
January 18, 2018

Review: "TIBCO BusinessEvents as CEP solution for complex problems"

Score 9 out of 10
Vetted Review
Verified User
Review Source
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
Read Fabio Martone's full review
November 22, 2017

TIBCO BusinessEvents Review: "How to get the business to adapt to change"

Score 7 out of 10
Vetted Review
Verified User
Review Source
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.
Read .john omahen's full review
January 24, 2018

TIBCO BusinessEvents Review: "Business Events, the prodigy of TIBCO!"

Score 7 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
January 19, 2018

"TIBCO BusinessEvents Review"

Score 4 out of 10
Vetted Review
Verified User
Review Source
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.

Read this authenticated review
January 18, 2018

TIBCO BusinessEvents: "TIBCO BE Product Review"

Score 5 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
November 14, 2017

TIBCO BusinessEvents Review: "BE isn't really worth it"

Score 2 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
November 06, 2017

TIBCO BusinessEvents Review: "A real Fast Data Engine!"

Score 6 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review
January 18, 2018

TIBCO BusinessEvents Review: "Eventful Business with BusinessEvents"

Score 7 out of 10
Vetted Review
Verified User
Review Source

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.
Read this authenticated review
October 30, 2017

TIBCO BusinessEvents Review: "BE as Business Roles Engine"

Score 7 out of 10
Vetted Review
Verified User
Review Source
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
Read this authenticated review
September 07, 2016

Review: "TIBCO BusinessEvents- Processing rules faster"

Score 6 out of 10
Vetted Review
Verified User
Review Source
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.
Read this authenticated review

TIBCO BusinessEvents Scorecard Summary

About 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

Has featureEnterprise Capable and Proven
Has featureRapid Application Development
Has featureEmpowering Business Users & Data Analysts

TIBCO BusinessEvents Videos (2)

TIBCO BusinessEvents Downloadables

TIBCO BusinessEvents Integrations

TIBCO BusinessEvents Competitors

IBM Streams, Drools, Software AG Apama, SAP Smart Data Streaming, Oracle Stream Explorer

Pricing

Has featureFree Trial Available?Yes
Has featureFree or Freemium Version Available?Yes
Has featurePremium Consulting/Integration Services Available?Yes
Entry-level set up fee?Optional

TIBCO BusinessEvents Support Options

 Free VersionPaid Version
Phone
Email
Forum/Community
FAQ/Knowledgebase
Social Media
Video Tutorials / Webinar

TIBCO BusinessEvents Technical Details

Deployment Types:On-premise
Operating Systems: Windows, Linux, Mac
Mobile Application:No
Supported Countries:Worldwide
Supported Languages: Arabic, German, French, Italian, Korean, Simplified Chinese