Detect: collecting and correlating events to identify actionable patterns or situations. An example might be repeated insurance quote requests from the same end user trying to get the best deal. Once a situation has been identified a decision needs to be made as to what to do – or what action to take. The action will depend on a number of factors and business rules can be used to decide the business outcome. Information can be added to the event data from other sources to provide the data the rule engine will need to make the decision.
Decide: interpreting the request from the decision service invocation and providing a response according to the rules and associated data. In the case of the repeated insurance quotes the decision might be to promote a particular insurance policy with specific discount terms or additional benefits. Alternatively the rule engine may determine that the user is attempting to obtain a type of policy for which this individual is not eligible.
The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
WebSphere Decision Server
Daniel Selman 2700022VQ3 5,889 Views
Duncan Clark has a nice piece on Decision Server, our packaging of Business Events with BRMS.