Tips and Tricks 
Normally, if the syntax or semantics is incorrect, or if there is spelling mistake, the configuration fails and prompts an error message. The tool continues to evaluate the subsequent configuration and outputs messages accordingly, based on whatever successful configuration that has been made.
The behavior results from the SAP Logging API error handling mechanism.
More information: Administrative Issues.
There is no system property to define this, nor there is a default physical file location specified for this. It is necessary to make one call in the program to load the properties.
It is not necessary to create and maintain a category or a location object. These objects are always accessible by making calls, such as Category.getCategory() and Location.getLocation(). The rest is done by the logging framework.
It is a good practice to use a static variable to store the handle for better performance, in case the source objects to be frequently accessed.
In general, no. Not for class variable definition. Consider the following:
Syntax
com.sapmarkets.foo.logs = + log[Console], log[File] log[Console] = ConsoleLog log[Console].formatter = ListFormatter log[File] = FileLog log[File].pattern = %t/trace.log log[File].formatter = formatter[Trace] formatter[Trace] = TraceFormatter formatter[Trace].pattern = %s: %24d: %m
The use of '+' sign does not apply to log assignments specified in the current file configuration content. Therefore, the sequence is important and the FileLog has priority.
Note
Assuming that no previous configuration is available.
More information: Syntax and Semantics of the Properties File.
Syntax
com.sapmarkets.foo.logs = + ConsoleLog com.sapmarkets.foo.logs = + FileLog
If you want to assign multiple logs, use a comma as a delimiter:
Syntax
com.sapmarkets.foo.logs = + ConsoleLog, FileLog