Oct
21
2009
Odd quotes: “TIBCO doesn’t have a rule engine”
Posted by Paul Vincent
… which came from a prospective customer who had based their research on top analyst Woodman’s famous Ripple report on Business Rule Engines. Which TIBCO didn’t participate in. So obviously we don’t have a rule engine (despite a 1-second Google returning over 17,ooo hits…).
To be fair, though, you won’t see “rule engine” under the TIBCO products list on the main web page. But then you won’t find “XML Processor” or “Application Server” in that product classification either…
So:
- if you are a “top analyst”, note TIBCO has a rules engine. And a rule (decision) management system. And an analytics suite. Really.
- if you are a “rule engine customer”, you might want to include TIBCO on your evaluation list…
Tags: rule engine, rule management
Rules | 21 October 2009 |
4 Comments
Other Links to this Post
RSS feed for comments on this post. TrackBack URI
By John S, October 21, 2009 @ 15:58
So you now have now your own decision management and rule engine? What happens to the Staffware suite and Rule Studio (OEM’d from Corticon)?
Are rules sharable between rules management tools? Tibco (via Corticon) allows to author only rules in a table format, what about the new Tibco rule engine? Do you provide several metaphors to author rules? Tools to manage rule change lifecycle and governance?
By Paul Vincent, October 22, 2009 @ 12:34
Hi John:
- TIBCO BusinessEvents Decision Manager is a fat-client application that allows decision tables to be defined, tested, and approved by business analysts (with an option of useing MS Excel for maintenance). Decision processing for events is a part of event processing which is why it is bundled within BusinessEvents.
- Decision Management workflows are controlled by the Rule Management Server - where workflows for decision table lifecycles (eg test, approval etc) are controlled. These workflows are themselves customizable BusinessEvents projects - indeed you could do rule management for your rule management process!
- TIBCO BusinessEvents also supports inference rules as well as queries, class models and state models, but these are not modelled at the business level (… yet) and are edited in the BusinessEvents IDE, not in the Decision Manager UI.
- TIBCO BusinessEvents Decision Manager is not related in any way to TIBCO iProcess Decisions (which as you state is OEM’d from another rule vendor). But iPD is restricted only to iProcess projects, whereas Decision Manager is embedded in the BusinessEvents event processing engine and accessible, via TIBCO BusinessWorks, from almost any type of application. For example, TIBCO ActiveMatrix applications requiring a managed decisioning capability can embed BusinessEvents decision engines in their SOA infrastructure. Note though that DM and iPD are not related and have different table formats, albeit both XML based…
- There is no current decision table standard (although TIBCO have contributed to the production rule standards OMG PRR and W3C RIF); however we are trying to start up a standard for such decision models at OMG, called DMN.
Further reading:
cep-vs-decisions-and-rules
standards-news-prr-and-dmn-updates
Cheers
By Jazon Samillano, January 26, 2010 @ 15:16
Hi Paul,
If you’re already using TIBCO ActiveMatrix BusinessWorks and iProcess, along with the iProcess Decisions/Insight, and you really do not have a business need for Complex Event Processing, would it still make sense to add BusinessEvents into the mix to help with the business rules, or would it be wholly gratuitous?
Thanks, Paul.
Jazon
By Paul Vincent, January 27, 2010 @ 03:56
Hi Jazon: use cases for CEP / TIBCO BusinessEvents in this scenario might be:
- monitoring the processes and services (see also the AM Service Performance Manager, effectively a BE application doing this for service control in AM)
- finding complex events that drive the BPM / use services (such as identifying fraud or exception cases)
- high performance routing and gateways (see also Active Service Gateway based on BE to route to AM services and thence BPM processes) for scenarios that may be too complex for BW
Cheers