How To Define Custom Rules for SOA WLDF
Last updated on JUNE 18, 2018
Applies to:Oracle SOA Suite - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
To provide detailed steps on how to create custom DFW (Diagnostic Framework) rules and leverage them from WLDF (WebLogic Diagnostic Framework) for SOA 11g.
The WebLogic Diagnostic Framework has been around for a while and was designed to help in identifying and resolving runtime issues in the server. Since WLS 10.3.3 WLDF has been augmented by the Diagnostic Framework (DFW) which allows for the automated collection of Diagnostic Dumps. These dumps are pre-defined and attached to 'rules' that listen for specific events from WLDF or Oracle Diagnostic Logging (ODL).
1. Server heap utilization exceeds 90%
2. A WLDF Watch has been configured to monitor a runtime mbean for this condition and is triggered
3. Notification is sent to DFW that the Watch was triggered along with 'header' information
4. DFW uses the 'header' information to determine which rule set applies to this particular Watch and routes the event
5. The relevant rules are evaluated for the condition. This is typically done by associating an error code in the Watch name.
6. If a rule is found that matches the error code reported then the associated Diagnostic Dumps are generated by the framework. There could be many rules for different error codes / messages, each with its own unique set of dumps associated
7. The Diagnostic Dumps are taken and then packaged in the ADR (Automatic Diagnostic Repository) as an 'incident'. The ADR can be found under <server_home>/adr/diag/ofm/<domain_name>/<repo_name>/incident
8. Incident can then be analyzed, packaged and uploaded to Support as needed
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms