Follow Up to SOA Selective Tracing Webcast
By ShawnBailey on Mar 09, 2012
The presentation recording can by found here
The schedule for future webcasts can be found here
There is a mistake in the slides on where to start WLST from. It should be started from 'oracle_common/common/bin', NOT wlserver_10.3/common/bin.
Q. Can the loggers for selective tracing participation be chosen through the WLST interface?
A. Yes. The loggers can be enabled or disabled using the WLST 'configureTracingLoggers' command. Full documentation on the WLST interface for Selective Tracing can be found here
Q. What is the best way to trace a login process?
A. Selective Tracing is only effective for ODL (Oracle Diagnostic Logging) loggers. Give that the actual login process is mostly handled by WebLogic Server, Selective Tracing will not capture this information because WLS does not implement ODL. To capture data about a login it is recommended to enable the WLS Authentication and Authorization debug loggers through the WLS console.
Q. Can tracing be enabled for WebLogic Server 10.3.5 for a particular managed server?
A. From Enterprise Manager Selective Tracing is a set at the domain level, however, the WLST interface offers an option on many of the commands called 'target'. Here you may specify a particular managed server for the tracing session. More information can be found in the product documentation referenced above. Note that a WLS only installation will not have the 'oracle_common' folder and without this Selective Tracing is unavailable.
Thank you to everyone who attended and to anyone who views the recording. If there are further questions or discrepancies please add a comment to this post for update.