Configuring QuickTrace Using WLST To configure QuickTrace using WLST, you

Managing Log Files and Diagnostic Data 12-31 Now that you have started the trace, you can view active traces, as well as former traces, as described in Section 12.6.2.1.2 .

12.6.2.1.2 Viewing Selective Traces Using Fusion Middleware Control You can view the

selective traces that are currently active and the history of selective traces. To view the selective traces: 1. From the Selective Tracing page, select the Active Traces and Tracing History tab. The tab shows a table with the active traces and a table with the tracing history, as shown in the following figure: 2. To view a trace, select it from the appropriate table. The Log Messages page is displayed, with the messages that were captured by Selective Tracing. You can search the messages, as described in Section 12.3.2 , and you can correlate the messages as described in Section 12.5 . In addition, you can download the messages to a file, as described in Section 12.3.3.1 . 12.6.2.1.3 Disabling Selective Tracing Using Fusion Middleware Control To disable selective tracing using Fusion Middleware Control: 1. From the navigation pane, expand the farm, then WebLogic Domain. Right-click the domain name and choose Logs, then Selective Tracing. 2. Select the Active Traces and Tracing History tab. 3. In the Active Traces table, select the trace and click Disable.

12.6.2.2 Configuring and Use Selective Tracing Using WLST

You can configure selective tracing, view traces, and disable selective tracing using WLST, as described in the following topics: ■ Configuring Selective Tracing Using WLST ■ Viewing Selective Traces Using WLST ■ Disabling Selective Traces Using WLST 12-32 Oracle Fusion Middleware Administrators Guide

12.6.2.2.1 Configuring Selective Tracing Using WLST You can configure loggers for

selective tracing and start tracing using the WLST configureTracingLoggers and startTracing commands. For the simplest case, you can configure and start a trace using the startTracing command. When you do so, the selective tracing includes all loggers enabled for selective tracing. For example, user1 receives errors when attempting to perform certain operations. To start a trace of messages related to user1 and to set the logging level to FINE, use the following command: startTracinguser=user1,level=FINE Started tracing with ID: 885649f7-8efd-4a7a-9898-accbfc0bbba3 The startTracing command does not provide options to include or exclude particular loggers. In this case, you can use the configureTracingLoggers command. This command allows you to configure selective tracing to include only particular loggers and particular Oracle WebLogic Server instances. Note that the options you specify apply to all current and active traces. For example, to configure selective tracing to include only security-related loggers: 1. Specify that all loggers be disabled, as shown in the following example: configureTracingLoggersaction=disable Configured 1244 loggers 2. Enable the security-related loggers, by specifying the pattern option with a regular expression: configureTracingLoggerspattern=oracle.security., action=enable Configured 62 loggers To see a list of the loggers that support selective tracing, use the WLST listTracingLoggers command, as shown in the following example: listTracingLoggerspattern=oracle.security. ------------------------------------------------------------------+-------- Logger | Status ------------------------------------------------------------------+-------- oracle.security | enabled oracle.security.audit.logger | enabled oracle.security.jps.az.common.util.JpsLock | enabled . . . 3. Use the startTracing command, specifying the users and the level. For example: startTracinguser=user1,level=FINE Started tracing with ID: a9580e65-13c4-420b-977e-5ba7dd88ca7f See Also: The following commands in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for complete syntax: ■ configureTracingLoggers ■ startTracing ■ listTracingLoggers