1. Log in to the Enterprise Manager console as a super administrator.
2. From the Setup menu, choose Security, then Administrators.
3. Select the appropriate administrator and click Edit.
4. Click Next twice to arrive on the Target Privileges page of the wizard.
5. Scroll down the page and click Add in the Target Privileges section of the page.
6. From the Search and Add: Targets popup dialog, select the appropriate targets for which the administrator should have access to view logs. Click Select.
7. From the Target Privileges section of the Target Privileges page of the wizard, select the targets to which you want to grant the “Ability to view Fusion Middleware Logs" target privilege and select Grant to Selected. Notice that the default target privilege automatically given for this target is View.
8. Select the Ability to view Fusion Middleware Logs target privilege and click Continue. Notice that the “Ability to view Fusion Middleware Logs" target privilege is also included as part of other target privileges (for example, Operator target privilege). So, depending on the responsibilities of the administrator, you may want to grant the Operator target privilege to the administrator.
9. Notice on the Target Privileges page of the wizard the appearance of the new privilege. Click Review and then Finish to conclude the operation.

You may find that you want to add custom log files for WebLogic Server such that those log files and messages appear in the Enterprise Manager Log Viewer. While Enterprise Manager does not support adding custom log files via the Log Viewer user interface, there is a way to do it outside of Enterprise Manager.

Normally the ODL LogQueryMBean automatically discovers the Weblogic server logs and any ODL log file defined in the logging.xml file associated with the Weblogic server. However, you can register additional log files with the ODL LogQueryMBean, so that these files can be viewed and/or downloaded from the Enterprise Manager Log Viewer.

When registering a new log file there are two options you can use:

• You can register a log file with an associated LogReader that can be used to parse the contents of the file. In this case the contents of the file can be viewed and searched from the main Log Messages page.

• You can register the path to the log file, but do not provide a LogReader to parse the contents of the file. In this case the contents of the file cannot be viewed and searched from the main Log Messages page, but you can view the raw contents of the file or download its contents from the Target Log Files page.

To register one or more additional log files you can create a file under directory:

DOMAIN_HOME/config/fmwconfig/servers/SERVER_NAME/diagnostics-registration

The file must have a .xml suffix and it should have contents similar to the following:

<?xml version='1.0' encoding='UTF-8'?>
<logs xmlns='http://www.oracle.com/iAS/EMComponent/ojdl'>
  <log path="/home/oracle/mylogs/my-odl-diagnostic.log">
    <logreader class="oracle.core.ojdl.reader.ODLLogReaderFactory">
    </logreader>
  </log>
</logs>

In this case the file is an ODL file and it is being registered with a LogReader. In addition to the ODL LogReader, there are a few existing log readers that can be used to read other formats.

You can also register a log without a log reader as seen here:

<?xml version='1.0' encoding='UTF-8'?>
<logs xmlns='http://www.oracle.com/iAS/EMComponent/ojdl'>
  <log path="/home/oracle/mylogs/my-other-diagnostic.log"/>
</logs>

You may use variables or a wildcard in the log path. The wildcard is denoted by "%*%", while a variable has the form of "%NAME%". Multiple occurrences of the same variable in the path must have the exact same value. If a variable appears only once, it will behave like a wildcard.

All log files registered in this way are associated with the server target in Enterprise Manager.

1. From the Enterprise menu, select Monitoring, select Logs, then select the target from the popup target selector.

   or

   From the Targets menu, select Middleware, click a farm. From the Farm menu, select Logs, then select View Log Messages.

   The Log Messages page displays a Search section and a table that shows a summary of the messages for the last hour.

2. In the Search Mode secstion, you can choose to search for only Live Logs, only Archive Logs, or Both.
3. In the Date Range section, you can select either:

   • Most Recent: If you select this option, select a time, such as 3 hours. The default is 10 minutes.

   • Time Interval: If you select this option, select the calendar icon for Start Date. Select a date and time. Then, select the calendar icon for End Date. Select a date and time.

4. In the Message Types section, select one or more of the message types.
5. You can specify more search criteria, for example, by providing text in the Message text field, so you can search on explicit words or patterns across log files.You can specify more search criteria, as described in Searching Log Files: Advanced Searches.
6. Click Search.
7. To help identify messages of relevance, in the table, for Show, select one of the following modes:

   • Messages - You can select an operator, such as contains and then enter a value to be matched.

     To see the details of a particular message, click the message. The details are displayed below the table of messages.

     To view related messages, select a message, then click View Related Messages and select by Time or by ECID (Execution Context ID).

   • Application ID - Groups messages related to a particular application.

   • ECID + Relationship ID - Groups messages by Execution Context (ECID) and Relationship ID (RID) which enables you to use log file entries to correlate messages from one application or across application server components. By searching related messages using the message correlation information, you can examine multiple messages and identify the component that first generated the problem.

   • Host - Groups messages associated with a particular host.

   • Host IP Address - Groups messages associated with a particular host IP address.

   • Incident ID

   • Message Type - Groups messages for each target based on the message type. It displays the total number of messages available for each message type, for example, ERROR, INCIDENT ERROR, WARNING, NOTIFICATION, TRACE, and UNKNOWN for every target.

   • Message ID - Groups messages based on the combination of Message ID, Message Type, Target, Message Level, Component, Module, and Organization.

   • Module - Groups the classes / modules that originated the message.

   • Target

   • Thread ID - Groups messages by Thread ID

   • User - Groups all messages for a particular user. For example, all the messages for user Jones will be listed before the messages for user Smith.