Monitoring Business Rules Service Engine Statistics

18-10 Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite and Oracle BPM Suite

18.6 Monitoring Decision Service Component Instances from a Composite Application

You can monitor Decision Service component instances from a composite application. Each Decision Service component instance has its own unique instance ID. This ID is in addition to the instance ID of the overall SOA composite application of which this Decision Service component is a part. Decision Service components are also called Business Rules components in the Oracle Fusion Middleware documentation. To monitor Decision Service component instances from a composite application: 1. Access a Decision Service component from a composite application through one of the following options: Note: To see the state with the correct information, you must set the Capture Composite Instance State option. You can change this setting on the SOA Infrastructure Common Properties page. Turning this feature on allows for separate tracking for running instances. However, this may impact performance. For information on setting the option, see Section 3.1, Configuring SOA Infrastructure Properties. From the SOA Infrastructure Menu... From the SOA Folder in the Navigator... 1. In the navigator, select soa-infra. 2. From the SOA Infrastructure menu, Select Home. 3. Click Deployed Composites tab. 4. In the Composite table, select a specific SOA composite application that includes a Decision Service component. 1. Expand soa-infra. 2. Select a specific SOA composite application that includes a Decision Service component. Monitoring Decision Service Components and Engines 18-11

2. The Component Metrics section on the composite dashboard provides a

high-level overview of each Decision Service component. This table includes columns showing the Component Type, the Total Instances, the Running Instances , and the Faulted Instances recoverable and nonrecoverable. 3. Select a Decision Service component in the Component Metrics section to display the corresponding Decision Service Component page. 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