Copyright © 2006, Oracle. All rights reserved Rule Engine

Copyright © 2006, Oracle. All rights reserved Introducing Business Rules Technology Business rules technology automates rules and policies. Business rules are: Extracted from processes and procedural logic Expressed declaratively Executed in an inference capable business rules engine Edited by business users Rules Engine Application Rule Author Rule Repository facts results

Copyright © 2006, Oracle. All rights reserved Declarative Rule Concepts Rule statements are easier to maintain than procedural code because they: Declare intent instead of coding logic Exclude control flow, which is determined by the rules engine Consider implementing rules for the following cases: Volatility: Impact: If a customer is a Premium customer, offer him or her 10% discount If a customer is a Gold customer, offer him or her 5% discount

Copyright © 2006, Oracle. All rights reserved Rule Inference Concepts Example of inference (A  B, B  C) implies (A  C) If a customer is a Premium customer, offer him or her 10% discount If a customer spends > 1000, make him or her Premium customer Customer Spends 1500 Premium Customer Offer 10% discount A B C B

Copyright © 2006, Oracle. All rights reserved Dictionary Defining Oracle Business Rules Development Concepts XML schema Facts Java classes Rule Author Variables Rule Repository Imports Generates using JAXB Create Create or open Data model Rule set Rules Define business policies

Copyright © 2006, Oracle. All rights reserved Expressing Rules with Oracle Rule Author Access Rule Author using the following URL:

Copyright © 2006, Oracle. All rights reserved Identifying the Structure of a Rule A rule has the following parts: 1.Rule name and description 2.Priority 3.Pattern definition 4.Condition 5.Rule action

Copyright © 2006, Oracle. All rights reserved Integrating Rules with a BPEL Process To integrate Oracle Business Rules with BPEL, perform the following steps: 1.Run the Decision Service Wizard to create a PartnerLink and invocation patterns. 2.Create a Decide activity to invoke the PartnerLink and create variable copy operations. Rules Rule repository BPEL process Decision service PartnerLink Assert facts Results Decide activity Input facts Output facts JDeveloper Decision Service Wizard 1 2

Copyright © 2006, Oracle. All rights reserved Order Booking If the customer has a Platinum status, then no manual approval is required. If the customer has a Gold status, then manual approval is only required for orders over $1000. If the customer has a Silver status, then manual approval is required for all orders, regardless of the order amount.

Copyright © 2006, Oracle. All rights reserved Reasons for Using the Rules Technology Agility –Rules are easier to change. –Rules are more responsive. Transparency –Rules are accessible. –Rules are consistently applied.+