红帽全球峰会此内容没有您所选择的语言版本。
16.11. Rule Set Examples
The rules are in a DRL file and execution following the stateless model:
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="OrderDiscountRuleService">
<property name="ruleSet" value="drl/OrderDiscount.drl" />
<property name="ruleReload" value="true" />
<property name="object-paths">
<object-path esb="body.Order" />
</property>
</action>
The rules are in a DRL file and execution following the stateless model:
- The rules are in a DRL file and execution following the stateful model. In this scenario, the client can send multiple messages to the rule service. For example, the first message might contain a customer object, with the subsequent ones each containing orders for that customer. Every time a message is received, the rules are run. (The client can add a property to the final message that tells the rule service to dispose of the contents of the working memory.)
- A single, synchronized session instance is shared across all of the concurrent executions of a stateful session deployment. This greatly limits the number of use-cases for the stateful model. If you require multiple, client-oriented sessions service deployment, consider using a jBPM or BPEL solution instead.
- Stateful sessions are not persistent .
- Stateful Sessions are not clustered .
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor" name="OrderDiscountMultipleRuleServiceStateful"> <property name="ruleSet" value="drl/OrderDiscountOnMultipleOrders.drl" /> <property name="ruleReload" value="false" /> <property name="stateful" value="true" > <property name="object-paths"> <object-path esb="body.Customer" /> <object-path esb="body.Order" /> </property> </action>
The rules are in a DRL file, the stateful model is used, audit logging is enabled and the JBoss Rules clockType , eventProcessingType and channels are configured to facilitate complex event processing .
Knowledge-base partitioning is not enabled since ruleMultithreadEvaluation is set to false (also note that ruleMaxThreads is set to 1).
Note
Complex event processing scenarios use the stateful model and are shared across all concurrent executions of a stateful session deployment.
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="OrderEventsRuleServiceStateful">
<property name="ruleSet" value="drl/OrderEvents.drl" />
<property name="ruleReload" value="false" />
<property name="stateful" value="true" >
<property name="ruleFireMethod" value="FIRE_UNTIL_HALT" />
<property name="ruleAuditType" value="THREADED_FILE" />
<property name="ruleAuditFile" value="myaudit" />
<property name="ruleAuditInterval" value="1000" />
<property name="ruleClockType" value="REALTIME" />
<property name="ruleEventProcessingType" value="STREAM" />
<property name="ruleMultithreadEvaluation" value="false" />
<property name="ruleMaxThreads" value="1" />
<property name="object-paths">
<object-path esb="body.OrderStatus"
entry-point="OrderStatusStream" />
<object-path esb="body.OrderInfo"
entry-point="OrderInfoStream" />
</property>
<property name="channels">
<!-- chan1 and chan2 are equivalent
(but timeout only applies if async is false) -->
<send-to channel-name="chan1"
service-category="cat1" service-name="svc1" />
<send-to channel-name="chan2"
service-category="cat1" service-name="svc1"
channel-class="org.jboss.soa.esb.services.rules.ServiceChannel"
async="true" timeout="30000"
set-payload-location="org.jboss.soa.esb.message.defaultEntry" />
<!-- chan3 is a custom channel -->
<send-to channel-name="chan3"
channel-class="com.example.MyChannel" />
</property>
</action>
The rules are in a Domain Specific Language format and the stateless execution model is employed:
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="PolicyApprovalRuleService">
<property name="ruleSet" value="dsl/approval.dslr" />
<property name="ruleLanguage" value="dsl/acme.dsl" />
<property name="ruleReload" value="true" />
<property name="object-paths">
<object-path esb="body.Driver" />
<object-path esb="body.Policy" />
</property>
</action>
The rules are in a Decision Table and the stateless execution model is employed:
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="PolicyPricingRuleService">
<property name="decisionTable"
value="decisionTable/PolicyPricing.xls" />
<property name="ruleReload" value="true" />
<property name="object-paths">
<object-path esb="body.Driver" />
<object-path esb="body.Policy" />
</property>
</action>
The rules are in a BRMS format, and the stateless execution model is employed:
<action class="org.jboss.soa.esb.actions.BusinessRulesProcessor"
name="RuleAgentPolicyService">
<property name="ruleAgentProperties"
value="ruleAgent/brmsdeployedrules.properties" />
<property name="object-paths">
<object-path esb="body.Driver" />
<object-path esb="body.Policy" />
</property>
</action>
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}