From the WebLogic Sever menu, select Logs Log Configuration.

Diagnosing Problems 16-19 ■ View menu —Select the columns to display in the table. Click on a particular column to sort contents up or down. ■ Show menu —Group messages by type or ID, or view them in chronological order. ■ View Related Messages —View messages related to those selected on the list. ■ Broaden Target Scope —Broaden the scope of messages displayed. You can broaden the scope to include all messages for the domain, WebLogic Server, or Farm. ■ Refresh menu —Specify an automatic or manual refresh rate. To view the contents of a generated log file: ■ Click the log file icon associated with a message to view the contents of that log file. ■ Click Target Log Files... to display the Log Files page and view or download the contents of all generated log files. For more information, see Viewing and Searching Log Files in Oracle Fusion Middleware Administrators Guide. Filtering Diagnostic Logs By default, the Log Messages page displays a summary of diagnostic messages logged over the last hour. To filter diagnostic logs: 1. Filter the messages that are displayed by updating the search criteria using the following fields: ■ Date Range —Set the date range to one of the following: – Most Recent—Set the amount of time to define the duration. – Time Interval—Set the start and end dates to define the interval. ■ Message Types —Select the message types that you want to display. ■ Add Fields —Add other message fields to your search criteria, such as Message ID, Component, and so on.

2. Click Search once you have set the fields, as desired.

The messages area is updated with the filtered results. For more information, see Viewing and Searching Log Files in Oracle Fusion Middleware Administrators Guide. Logging Oracle WSM Debug Messages To debug Oracle WSM, pass one of the following properties when starting WebLogic Server, as required. For more information, see Starting and Stopping Servers in Managing Server Startup and Shutdown for Oracle WebLogic Server. Note: Enabling one or more of these properties may negatively impact performance for very large messages. When enabled, Oracle WSM creates temporary buffers which will result in additional load on the Java garbage collector.