16.5. Using Rule Services with JBoss Rules
- the amount of client code required to integrate the rules into your application environment is dramatically reduced.
- rules can be accessed from either an action chain or from within an orchestrated business process.
DroolsRuleServiceaction classes, the latter of which also implements the
BusinessRulesProcessorclass allows rules to be loaded from the class-path. These rules are defined in
.dslfiles, and also in decision tables (which come in
.xlsformat). These file-based rules exist primarily for the purpose of allowing you to test prototypes. There is no way to specify multiple rule files for a single
BusinessRulesProcessoraction. More complex rule services require the use of the JBoss Rules
KnowledgeAgentto access rule packages from either the Business Rules Management System or from the local file system. Rule packages can contain thousands of rules from different sources, including these:
- the JBoss Business Rules Management System
- domain-specific language (DSL) files
- decision tables
KnowledgeAgentapproach on production systems.
ruleAgentPropertiesfile's poll property). You now configure it globally via the org.jboss.soa.esb.services.rules.resource.scanner.interval property, found within
esb.deployer/jbossesb-properties.xml. (The default value is 60.) This means that every sixty seconds, the system checks for resource changes across all KnowledgeAgents.
username=admin password=admin enableBasicAuthentication=true