My Oracle Support Banner

How to enable TRACE / DEBUG logging in Oracle SOA Suite 11g (inc. VIDEO) (Doc ID 1325672.1)

Last updated on JULY 18, 2018

Applies to:

Oracle SOA Platform - Version 11.1.1.1.0 and later
Oracle SOA Platform - B2B (Business to Business) - Version 11.1.1.1.0 and later
Oracle(R) BPEL Process Manager - Version 11.1.1.1.0 and later
Information in this document applies to any platform.

Goal

There maybe times when Oracle Support has requested you to provide TRACE level logs for a SOA Suite component in order to help you debug an issue that you're having within your system.

This note guides you through making those TRACE level changes to the SOA Suite, and shows you how to export the logs which you can review either within the Enterprise Manager Fusion Middleware Control (fmwctl) (/em) url, or offline as a file on your local filesystem; and also as something that you can potentially attach to an Oracle Support SR for review.

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
 
Message Type Level Description
 Log Level Performance Impacts
 Oracle SOA Suite loggers / descriptions
(please note that not all loggers are directly visible under their parent; for example: .bpel (activities).  
This exists under oracle.soa.bpel.engine.bpel and not oracle.soa.bpel.bpel.  
If in doubt, enter .<keyword> (eg: .bpel) in the search box and click the search button to find the specific logger in the list below.
Also note there are more loggers available than the shortened list below which are specific to the SOA Suite) 
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.