Now that Impact is over and IBM BPM 7.5 has been officially announced I can talk a little more about its rules capabilities. If you want a general overview of IBM BPM 7.5 Sandy Kempsley has a nice write up here and you can watch Phil Gilbert here.
For the past few months I have been leading a small, but very dedicated, team that has been improving the consumability of core ILOG BRMS components/APIs and supporting the BPM team as they perform the integration of the ILOG components within the BPM design and runtime. I believe it will lead to a considerably better rules experience for BPM customers as well as provide a smooth migration path to the full ILOG BRMS, if and when required. Of course it also just makes good engineering sense to share ILOG's expertise and code in the business rules space with our comrades in the BPM team.
The rules capabilities embedded within BPM have the following characteristics:
- Rules have the same life-cycle as their process and are transparently persisted with the calling process
- Process variables are automatically available to rules
- Simplified execution semantics using explicit ordering of the rules and the sequential execution algorithm, executed by the standard JRules Rule Execution Server running in embedded JSE mode
- Automatic/transparent generation of BOM/VOC from process variable definitions
- Ability to export an executable Rule Studio rule project for a set of BAL rules, providing a simple migration path to rules managed by the BRMS and a service oriented execution pattern
I am excited to see how the technology gets used by BPM customers, particular as for many it will be their first exposure to a "real" business rules capability! ;-)