Viewing Selective Traces Using WLST After you have begun a trace, you can see Disabling Selective Traces Using WLST To avoid excessive logging in the

13-4 Oracle Fusion Middleware Administrators Guide within the ADR. For example, each Managed Server and Administration Server has an ADR home directory. The ADR root directory is known as ADR base. By default, the ADR base is located in the following directory: DOMAIN_HOMEserversserver_nameadr Within ADR base, there can be multiple ADR homes, where each ADR home is the root directory for all incident data for a particular instance of Oracle WebLogic Server. The following path shows the location of the ADR home: ADR_BASEdiagofmdomain_nameserver_name Figure 13–1 illustrates the directory hierarchy of the ADR home for an Oracle WebLogic Server instance. Figure 13–1 ADR Directory Structure for Oracle Fusion Middleware The subdirectories in the ADR home contain the following information: ■ alert: The XML-formatted alert log. ■ incident: A directory that can contain multiple subdirectories, where each subdirectory is named for a particular incident. The subdirectories are named incdir_n, with n representing the number of the incident. Each subdirectory contains information and diagnostic dumps pertaining only to that incident. ■ others: Other subdirectories of ADR home, which store incident packages and other information. Note: ADR uses the domain name as the Product ID and the server name as the Instance ID when it packages an incident. However, if either name is more than 30 characters, ADR truncates the name. In addition, dollar sign and space characters are replaced with underscores. Diagnosing Problems 13-5

13.1.2.2 Diagnostic Dumps

A diagnostic dump captures and dumps specific diagnostic information when an incident is created automatic or on the request of an administrator manual. When executed as part of incident creation, the dump is included with the set of incident diagnostics data. Examples of diagnostic dumps include a JVM thread dump, JVM class histogram dump, and DMS metric dump.

13.1.2.3 Management MBeans

The Diagnostic Framework provides MBeans that you can use to configure the Diagnostic Framework. For example, you can enable or disable flood control and you can configure how many incidents with the same problem key can occur within a specified time period. For information about using the management MBeans to configure the Diagnostic Framework, see Section 13.3 . You can also use the MBeans to query and create incidents, discover the list of available diagnostic dump types, and execute individual diagnostic dumps.

13.1.2.4 WLST Commands for Diagnostic Framework

The Diagnostic Framework provides WLST commands that you can use to view information about problems and incidents, create incidents, execute specific dumps and query the set of diagnostic dump types. For more information, see: ■ Section 13.4.2.1, Viewing Problems ■ Section 13.4.2.2, Viewing Incidents ■ Section 13.4.3.1, Listing Diagnostic Dumps ■ Section 13.4.3.2, Viewing a Description of a Diagnostic Dump ■ Section 13.4.3.3, Executing Dumps ■ Section 13.4.4.1, Creating an Incident Manually ■ Diagnostic Framework Custom WLST Commands in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference To use the custom WLST Diagnostic Framework commands, you must invoke the WLST script from the Oracle Common home. See Section 3.5.1.1 for more information.

13.1.2.5 ADCRI Command-Line Utility

The ADR Command Interpreter ADRCI is a utility that enables you to investigate problems, and package and upload first-failure diagnostic data to Oracle Support, all within a command-line environment. ADRCI also enables you to view the names of the dump files in the ADR, and to view the alert log with XML tags stripped, with and without content filtering. ADRCI is installed in the following directory: UNIX MW_HOMEwlserver_10.3serveradr Windows MW_HOME\wlserver_10.3\server\adr See the following sections for information about using the ADCRI command-line utility: ■ Packaging an Incident ■ Purging Incidents 13-6 Oracle Fusion Middleware Administrators Guide

13.2 How the Diagnostic Framework Works

The Diagnostic Framework is active in each server and provides automatic error detection through predefined configured rules. Oracle Fusion Middleware components and applications automatically benefit from this always-on checking. Incidents are automatically detected in two ways: ■ By the incident detection log filter, which is automatically configured to detect critical errors. ■ By the WLDF Watch and Notification component. The Diagnostics Framework listens for a predefined notification type and creates incidents when it receives such notifications. For information about configuring WLDF Watch and Notification, see Section 13.3.2 . ■ Programmatic incident creation. Some components create incidents directly. Figure 13–2 shows the interaction when the incident is detected by the incident log detector. It shows the interaction among the incident log detector, the WLDF Diagnostic Image MBean, ADR, and component or application dumps when an incident is detected by the incident log detector. Figure 13–2 Incident Creation Generated by Incident Log Detector See Also: ■ The chapter ADRCI: ADR Command Interpreter in Oracle Database Utilities ■ The chapter Managing Diagnostic Data in the Oracle Database Administrators Guide Log File Diagnostic Rules Managed Server WebCenter ODL Log Handler Incident Detection Log Filter Application Dump WLDF Diagnostic Image MBean 1 Register Log messages 2 3 Filter Write 4 Component Dump ADR 5 Create Incident 7 Write 6 Execute 8 Invoke 6 Execute 9 Write