rule-engine

I am looking to integrate with a 'Generic Rules Engine' based on the request of a customer. I think the objective is to allow business stakeholders to add 'Rules', and have those be incorporated into an overall metric calculated on a dataset. So far, the Rules i have heard seem like straightforward snippets of logic in the code. I suppose the drawback is that even though simple, this would still need to be coded... (as opposed to some kind of runtime or data driven rule specification automatically used in the analysis.) hopefully not too vague - but anyone have any success with such a thing?

I have created a rule whose "when" condition is as follows :- when $map: Map(this["key1"].equals("value1")) and Map(this["key2"].equals("value2")) then ... The above condition is working fine. Now how do I add multiple boolean conditions in a rule? For eg. The above rule could be summarized as : a and b so if I want to create a rule : (a and b) or c then what would be actual drl syntax for it. I am new to drools so kindly help me with the syntax of the rule (a and b) or c. I did create a syntax when $map: Reindexing((Map(this["key1"].equals("value1")) and Map(this["key2"].equals("value2"))) or

I've read a lot of documentation of JBoss Drools but cannot find a definitive answer as to if all rules are executed concurrently (certainly they are fired concurrently). More specifically, for a single input and a rule set of say 1000 rules, do the "when" conditions and the "then" conditions in each rule, execute sequentially one by one, or in parallel at the same time. On the one hand the rete algorithm implies parallelism, certainly when the select nodes are collapsed. However after the nodes are optimized is the evaluation sequential? And the beta memory and join nodes look like they

I am about to dive into a rules oriented project (using ILOGs Rules for .NET - now IBM). And I have read a couple different perspectives regarding how to set up the rules processing and how to interact with the rule engine. The two main thoughts I have seen is to centralize the rule engine (into its own farm of servers) and program against the farm via a web service API (or in ILOG's case via WCF). The other side is to run an instance of the rule engine on each of your app servers and interact with it locally with each instance having its own copy of the rules. The up side to centralization is

I'm starting a project whith Drools and Drools Guvnor. My rules are deployed in drools guvnor. My rule engine instance can access those rules via the pkg file exposed by drools Guvnor when you do a package release build and release. This is all working fine, what I'm looking for is a solution for disabling a rule at runtime. The only solution I have right now is to go to guvnor, archive the rule and do a build + release of the package containing that rule. Isn't there another strategy ? There are a few ways of solving this, depending on your requirements and architecture. One way is to define