In JDeveloper, we could write our application logging to logs for debugging and viewable from JDeveloper.
When we deploy to Standalone weblogic server, we cant find our logging.
Of the 3 loggers (Msg Catalog, nonCatalog, Commons log API),
Which logging mechanism is the best practice used logging for development environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
Which logging mechanism is the best practice used logging for production environment ? Does it print to AdminServer.log ? If not, how can we accomplish that printing app log to AdminServer.log ?
You can use ADF diagnostics logging is controlled via the usage of the jbo.debugoutput parameter. Using this parameter with the console value, i.e. -Djbo.debugoutput=console.
this link will be helpful to you
people commonly Log4J for their logging,Like Commons Logging, SLF4J, or the default Java Logging API. But if you're working with Oracle's Application Development Framework, there is another option as well: ADF Logging.
ADF Logging is a logging mechanism, embedded in the ADF framework. It wraps the Java Logging API, but throws in a few extra methods and some JDeveloper and (Weblogic) Enterprise Manager features.
the following one demo video from oracle site its very useful.