TIBCO BusinessEvents- Processing rules faster
September 07, 2016

TIBCO BusinessEvents- Processing rules faster

Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO BusinessEvents

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.
  • Using Rules Engine provided a consistent interface for logic evaluation to different users
  • Java based platform provided easy integration capabilities with existing system
  • Most of the existing resources were Java trained, so they could start working with BusinessEvents without a huge learning curve.
You need a full orchestration suite to perform pre-enrollment checks before storing [them] into the system of records. TIBCO BusinessEvents was bought along with TIBCO BusinessWorks (BW) to design the end to end flow for member contract processing. We were able to get down the processing time to 12 seconds and were also able to increase the first pass rate.
  • 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.