Weitere Kapitel dieses Buchs durch Wischen aufrufen
Target audience Developer, software architect In this chapter you will learn How testing is supported in ILOG JRules 7.1 How to verify during authoring phase the rule consistency How to tune the rule execution performance Key points Rule analysis uses a search engine, which helps to find inconsistencies among a ruleset, like rule never selected, wrong operator, redundant rules … Searching for inconsistencies within a ruleset is an important capability to improve the ruleset quality. Semantic queries help to search for rules impacting others. Decision Validation Service offers the capability for the business users to test the ruleset in isolation and execute simulation: tests compared using key performance indicator.For each ruleset, assess with business users the need of using DVS. Business users use RTS and DVS together to update, rules, data set, scenarios, and to execute the suite of scenarios against a given ruleset.Performance of a rule engine is impacted by the number of rules, number of conditions in the rules, and the number of objects inserted in the working memory. Most business applications do not have performance problem. When needed, it is always possible to perform some tuning to improve performance.
Bitte loggen Sie sich ein, um Zugang zu diesem Inhalt zu erhalten
Sie möchten Zugang zu diesem Inhalt erhalten? Dann informieren Sie sich jetzt über unsere Produkte:
See the jrules-ssp-WAS7.ear for WAS or testing.war for Tomcat in dvs/applicationservers folder.
JSR-237 specifies the Work Manager API, which hides the thread API, and leverage in an application server, the contract of the container to manage the pool of thread, and the thread life cycle. The Work Manager API defines Work as a unit of work, which we want to execute asynchronously, which is the case for ruleset parsing.
- Rule Testing with JRules
Mr. Jérôme Boyer
Prof. Hafedh Mili
- Springer Berlin Heidelberg
- Chapter 15
Neuer Inhalt/© ITandMEDIA