Collecting Data: Configuring ODM Logging in WAS standalone server

Answer

ODM L2 and L3 support team may ask you to enable a more detailed log level in order to troubleshoot your issue.
Logging for ODM is handled through the Java Common Logging facilities (java.util.logging package). You can enable log level at a general level for the ODM application, or specify specific logging level for certain ODM packages.

The easiest way to enable more detailed logging for ODM is to go and configure the log level in the WAS Administration Console.

Under Troubleshooting > Logs and Trace select your [ODMServerName], for instance SampleServer.


On the SampleServer page, under General Properties, select Diagnostic trace, then under Additional Properties, select Change Log detail levels



By default, the log level is set to *=info, that is, it is set to INFO level for all components.
You need to know that the possible log levels are: SEVERE, WARNING, INFO, FINE, FINER, FINEST, OFF or ALL. The level OFF is used to turn off logging. Level ALL is used to enable logging of all messages.

Unfold the Components and Groups and scroll down to the ilog.rules.* packages to select which ODM module you want to set a specific trace level for.
Then once you have selected a given package, use the right click menu Message and Trace Levels to select the trace level you want.
For instance, as illustrated in the below screenshot, if you select the ilog.rules.teamserver.* package and set the trace level FINE with the right click menu, this will automatically add "ilog.rules.teamserver.*=fine" in the ':' separated list of log detail levels.