Logger.properties file
Use the Logger.properties file to set logger attributes for our component.
The properties file is loaded the first time the Logger.getLogger(loggername) method is called within an application. The Logger.properties file must be either on the WebSphere Application Server class path, or the context class path.
The logging subsystem uses Common Base Events to represent all the messages in the WAS activity.log file. We can specify our own event factory template to be used with your loggers. Use the eventfactory property in your Logger.properties file. See Sample Common Base Event template for details on the Common Base Event template.
By convention, the name of the event factory template file should be the fully qualified package name of the package using the template. The name of the file must end with the .event.xml extension. For example, a valid event factory template file name for the com.abc.somepackage package is:
com.abc.somepackage.event.xmlWhen we specify the property value for the eventfactory property in the Logger.properties file, include the full path name with no leading slash relative to the root of our class path entry. Do not include the .event.xml extension.
For example, if the template files from the previous example are located in the com/abc/templates directory, the valid value for the eventfactory property is:
com/abc/templates/com.abc.somepackageFinally, if this event factory template file is used by the com.abc.somepackage.SomeClass logger, then the following entry will appear in the Logger.properties file:
com.abc.somepackage.SomeClass.eventfactory=com/abc/templates/com.abc.somepackageIBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .
Logging Common Base Events in WAS Use High Performance Extensible Logging to troubleshoot applications Sample Common Base Event template Logger.properties file for configuring logger settings Log level settings