In the Logs column, click a specific log to access the Log Messages page with Monitoring Business Rules Service Engine Deployed Components Monitoring Decision Service Component Instances from a Composite Application

Monitoring Decision Service Components and Engines 18-15

5. Enter an Order ID, for example 1001, in the Value field in the Input Arguments

section on the Test Web Service page and click the Test Web Service button. Based on the input Order ID, the service invokes a BPEL process instance containing the details of the Order ID, and the rule that is relevant to the order details is executed. 18-16 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

6. Click Launch Message Flow Trace under the Response tab to open the Flow Trace

page.

7. Click the Decision Service component instance called DiscountDictionary in the

Trace section to view the actual rule execution trace. Monitoring Decision Service Components and Engines 18-17 The following graphic shows the execution trace for the Decision Service component called DiscountDictionary.

8. Click the Show rule set stack states in audit trail checkbox to view further details

of the rule execution. Note: You can also view the values of composite variables before and after invocation of business rule component. You need to click the BPEL process component instance in the Flow Trace page, and then click the relevant payload. In this case, the BPEL component name is FODOrderProcessingProcess. 18-18 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite The development-level trace report displays the fact name, activated rule, as well as the pushed and popped ruleset names. The following table lists the entries of the trace report: Element Description Invoked Decision Service Name Displays the name of the decision service component that is invoked. Asserted Fact Displays the name of the fact that is passed by the BPEL service to the decision service component. This is based on the input parameter provided by the user, which as per the example is the Order ID 1001. Activated Rule Displays the name of the rule that is activated, along with the name of the fact that activated the rule. Pushed ruleset Displays the name of the ruleset that has been invoked when the fact is asserted. Fired rules in Ruleset Displays the name of the ruleset whose rule is executed. Fired rule Displays the name of the rule that is executed. Modified fact Displays the name of the fact that has been modified as a result of the rule execution. This modified fact is then passed by the decision service component to the BPEL service. Popped ruleset Displays the name of the ruleset for which execution is complete and so, the ruleset is taken out of the execution queue. Monitoring Decision Service Components and Engines 18-19

18.7.2 Tracing Rule Execution at the Production Audit Level

Setting the audit level to Production provides a truncated report on the rule execution trace. It only displays the ruleset and the rules that have been fired and does not display details about facts, rule activation, and so on. The process of production-level tracing is similar to the development-level tracing. However, for Production-level tracing, you need to do the following: In Fusion Middleware Control, after opening the composite, select Production from the Composite Audit Level of the Settings menu. The following graphic shows the Flow Trace page that displays the trace report. The Production-level trace report contains only the name of the ruleset and the rules that were fired. In addition, the Show rule set stack states in audit trail checkbox that provides a drill-down detailed trace report is unavailable in the Production-level trace report. Notes: The entry Invoked Decision Service Name appears differently in different scenarios: ■ For AS10.1.3.x to AS11 upgraded rules dictionaries with AssertExecuteWatch patterns, the entry appears in the trace report as Invoked Decision Service. ■ For AS10.1.3.x to AS11 upgraded rules dictionaries with CallFunction patterns, the entry appears in the trace report as Invoked Decision Function. ■ For AS11 created dictionaries, the entry is displayed as Invoked Decision Function.