Set Logging Levels and Download Diagnostic Logs

You can set logging levels and download diagnostic logs in Oracle Integration. You can also obtain the impacted POD name from the diagnostic logs.


  • Changing logging levels from their default values can fill up disk space and degrade system performance. Ensure that you reset the logger level to the default level when you have completed troubleshooting.

  • When you use the search facility, only the first ten results are displayed, even if there are more.

To set logging levels and download diagnostic logs.

  1. In the navigation pane, click Integrations, then click the < sign next to Designer.

  2. Click Settings, then click Logging Levels.

    The loggers available for configuration are displayed. If the logger level is inherited from a parent logger, that information is displayed.

  3. Change the logger level of any logger.

  4. To revert to the previous setting before clicking Save, click Revert.

  5. Click Save.

    A message is displayed at the top of the page:
    Logger levels updated successfully. Be sure to reset logger level to the default level when troubleshooting has been completed.
  6. Click the home icon icon, then click the Monitoring diagram.


    You can also access the diagnostic logs directly from the Integrations page if your integration activation fails. Click the Download diagnostic logs link at the top of the page. See Activate an Integration.
  7. Click Download Diagnostic Logs.

    Note that the downloaded ZIP file name includes the WebLogic Server domain name (the same as your POD name) prepended to the front. For this example, the POD name of domain_ics_expanded is prepended to the front: This enables you to know the POD from which the file is being downloaded.

    You can also get the POD name from inside the AdminServer-diagnostic.log file that is included in the ZIP file.

  8. Unzip the file, and within the expanded directory structure, open AdminServer-diagnostic.log.

  9. If the logger level is set to NOTIFICATION, this file also includes the WebLogic Server domain name (the POD name), which is written to the file every 30 minutes (for this example, domain_ics_expanded is also the name).
    [2016-11-09T12:00:00.413-08:00] [AdminServer] [NOTIFICATION] [ICS-10071] [oracle.ics] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: f1xa8364-21dc-4c08-8843-a57b23b9bde2-000051f5,0] [APP: icswebapp] Weblogic domain name is "domain_ics_expanded".

    An environment.txt file is part of the downloaded ZIP file. It contains details regarding the Oracle Integration, including the version, mode, and POD name.