Oim11g - Best Practice for Logging

Question

Hello all,
want to know  the best practice or common usage of error logging in oim11g. As we know that oim has some sequence to run processes that will end in Java. For the best practice, where and when should I create the log? Should I create log inside each function called by oim adapter? If I make a sysout at the beginning of function, parameter names and values, e.getMessage() inside catch(Exception e) and at the end of function, is it okay? Or is there any better implementation? Using sysout or log4j, commons logging, etc.
in my idea (in each function):
<function_name>::BEGIN
- Time: <dd-MMM-yyyy>
<function_name>::PARAMETER
- <param_name1>: <param1_value>
- <param_name2>: <param2_value>
- <param_name3>: <param3_value>
if error, inside throw{}
<function_name>::ERROR
- Message: <e.getMessage()>
<function_name>::END
is it good?

Answer 1

This is what i've been doing with 11g logging.  In every custom code class i run, i use this to declare my logger:
private final static Logger LOGGER = Logger.getLogger(<Class_Name>.class.getName().toUpperCase());  // Replace <Class_Name> with the actual class name
This lets me go go the enterprise manager and make changes to the logging level once the class has been used.
You can then use the following code:
LOGGER.log(Level.INFO, "Insert Information Message Here");
LOGGER.log(Level.CONFIG, "Insert More Detailed Debugger Information Message Here");
LOGGER.log(Level.WARNING, "Insert Error Message Information Here", e); //e is your exception that is caught
Personally, i like to put a start and end output in my logging, and then any details in the middle, i use the CONFIG level.  This lets me know pieces are running successfully, and only need to see the details during testing or if needed.  When deployed to production, i set the logger to WARNING level to only know about the problems.
By using these, you can set your logger appropriately in the enterprise manager to output more detailed when needed.
-Kevin