How to enable TRACE / DEBUG logging in Oracle SOA Suite 12c And Oracle Service Bus 12c
(Doc ID 1903013.1)
Last updated on FEBRUARY 06, 2024
Applies to:
SOA Suite Cloud Service - Version 12.1.3.0 and laterSOA on Marketplace - Version 12.2.1.4 and later
Oracle Service Bus - Version 12.1.3.0.0 and later
Oracle SOA Suite - Version 12.1.3.0.0 and later
Information in this document applies to any platform.
Goal
Oracle Support has requested you to provide TRACE level logs for a SOA Suite component in order to help debug an issue that you're having within your system.
This document provides the steps to making those TRACE level changes to the SOA Suite for SOA BPEL or OSB.
Note: Remember that the most detailed logging level writes vastly more information to the managed server logs on the filesystem and therefore should typically only be enabled when you have sufficient disk space and normally only for the duration of your debugging process. It's recommended to return the loggers from TRACE:32 back to NOTIFICATION:1 or whatever they were set to earlier.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| How to enable TRACE for SOA |
| How to enable TRACE for OSB |
| How to access the TRACE logs |
| TRACE logger details for SOA and OSB |
| References |