Adding, Editing, and Removing Log
Controllers 
Use
A log controller controls the output to logs. Log controllers are the objects you call to write messages. To this end, log controllers provide you with methods for associating logs with them and for controlling the actual writing of messages. Two types of controllers are available:
· Location – describes messages that originate from delimited source code areas. Above all, it is used to emit trace messages.
· Category – describes messages specific to distinguished problem areas. Above all, it is used to emit log messages. Typical problem areas are databases, networking, security auditing, and others.
This procedure describes how you manage the log controllers using the SAP NetWeaver Developer Studio.
Prerequisites
· An installed and running NetWeaver Developer Studio.
· An already created EAR project. For more information about how you can create an EAR project using the SAP NetWeaver Developer Studio, see Creating Enterprise Application Projects.
Procedure
...
1. In the J2EE Explorer tab, choose your EAR project.
2. From the context menu, choose New ® SAP logging configuration.
The log-configuration.xml appears in the project tree.
3. Choose the Log Controller tab from the right-hand pane.
Adding a New Controller
...
1. Choose the Log Controllers folder.
2. Choose Add.
The new controller appears in the Log Controllers tree. A tree structure is generated along with the new controller, which contains the Log Filters section for specifying log filters and the Associated Destinations section (this section is divided into References Destinations and Anonymous Destinations sub-sections), for configuring associated destinations.
3. Choose the newly created log controller.
Several fields appear on the right-hand side of the Log Controller tab. Use them to specify the parameters of the new controller.
4. In the Controller name field, enter the name of the new controller.
Categories are named according to the hierarchical structure known from file systems. You can group together all categories of log messages concerned with one particular issue. The category name must be separated by “/”, for example /System/Database (always starts with ‘/’).
Locations are named according to the hierarchical structure known from Java packages. The category name must be separated by “.”, for example, com.sap.yourPackage.Class.
5. In the Bundle name field, assign a resource bundle name to this log controller.
If a resource bundle is assigned, language-independent log messages can be written.
6. Use the Effective severity dropdown box to set the required severity level. For more information about severity levels, see Log Severities.
7. Use the Minimum severity dropdown box to set the minimum severity of this controller with respect to a location. If its current maximum severity is lower than the argument, the former is set to the argument.
8. Use the Maximum severity dropdown box to set the maximum severity of this controller with respect to a location. If its current minimum severity is higher than the argument, the former is set to the argument.
9. Use the Relative severity pane to set a relative severity for this controller.
...
a. In the Severity Name field, enter the name of the new relative severity.
b. From the Severity Value dropdown box, select the required value.
10. Choose Save.
In the Log Controller tab you can add filters and associated destinations to your controller. For more information, see Adding Filters to a Controller and Adding Associated Destinations to a Controller.
Editing a Controller
...
1. Choose the controller you want to edit.
2. Modify the required parameters using the fields in the right-hand side of the Log Controller tab.
3. Choose Save.
Removing a Controller
...
1. Choose the controller you want to remove.
2. Choose Remove.
A dialog box appears. Choose OK to confirm that you want to remove this controller.
3. Choose Save.