Preventing looping and inefficient rule execution

This recipe gives guidance on how to avoid rule executions that will loop, potentially indefinitely! We'll use an inbound XML and a local RL (Rule Language) fact as an example.

Getting ready

You'll need access to an SOA composite containing an Oracle Business Rules component in JDeveloper to apply this recipe. We'll assume that you have an XSD schema with an input RequestInput containing two strings called input and bonus, and an output ResponseOutput containing a string called output. These aren't efficient, but will serve as an example. We'll step through adding a rule to a composite and creating an RL fact.

How to do it...

To remove potential circular references, perform the following steps:

1. Open the SOA composite. Right-click on the project, and select Business Rules (Service Components); use the search box if it is not immediately available.

   

2. Give the rule a name, and click on the green plus (+) icon to add RequestInput to the Input and ResponseOutput...