Monitoring Business Rules Service Engine Instances

18-12 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite For more information, see Section 1.2.3, Introduction to SOA Composite Application Instances.

18.7 Monitoring Business Rule Tracing

You can use Oracle Enterprise Manager Fusion Middleware Control to perform rule execution tracing. For more information about accessing and using Fusion Middleware Control, see Chapter 2, Getting Started with Administering Oracle SOA Suite and Oracle BPM Suite. A rule execution trace is a mechanism of tracing Oracle Business Rules service engine events that occur during the evaluation of rules. The types of events traced are: ■ Fact operations assert, retract, and modify ■ Rules execution ■ Rule activation ■ Ruleset stack changes ■ Rule compilation ■ Reset required for maintaining state during analysis Each trace contains information about the event that it traces. For example, a rule trace entry for an executed rule consists of: ■ Rule name RL name Monitoring Decision Service Components and Engines 18-13 ■ Execution sequence number ■ List of fact IDs for the facts that matched this rule ■ Timestamp in milliseconds Rule execution trace audit levels are the same as the audit levels supported in the SOA Infrastructure: ■ Off: Rule execution tracing is disabled. The decision component instance is not created at all. ■ Development: Full rule execution tracing that contains all the details about facts listing, operations such as modify and assert, rule activation, pop or push rulesets, and so on. It also provides a list of fact IDs on which the executed rules are matched. See Section 18.7.1, Tracing Rule Execution at the Development Audit Level for an example. ■ Production: The executed rules are traced. All the details about facts, rule activation, pop or push ruleset are not available. The trace do not contain a list of the matching facts IDs. See Section 18.7.2, Tracing Rule Execution at the Production Audit Level for an example. You can set audit levels either at the SOA Infrastructure level or at the composite level. See Section 3.1, Configuring SOA Infrastructure Properties for SOA Infrastructure audit level configuration information. See Section 1.4.1.1, Introduction to the Order of Precedence for Audit Level Settings for a discussion about audit level precedence when set at the SOA Infrastructure level and the composite level. The following sections discuss setting audit levels at the composite level for the purposes of rule execution tracing.

18.7.1 Tracing Rule Execution at the Development Audit Level

Setting the audit level to Development enables you to view all the details pertaining to a rule that has been executed. To perform a development-level rule execution trace: 1. Open the composite application in Oracle Enterprise Manager Fusion Middleware Control. A list of the recent composite instances is shown on the composite Dashboard page.

2. Click the Settings list, select Composite Audit Level, Development to set the

trace level as Development at the composite level. 18-14 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

3. Click Yes in the Confirmation dialog.

4. Click Test and then client to invoke a test instance of the composite to view the

decision traces corresponding to different input parameters, such as the Order ID.