
Using the procedures below you can:
Configure at runtime the severity of log controllers, the whole system tree, and a certain system instance
Perform sophisticated filtering of log controllers
Before changing the severity of a log controller, bear in mind that:
If you change the severity of a log controller at a system (template) level, the new severity will be valid on all instances for this log controller.
If you change the severity of a log controller for a particular instance, and this severity is different from the ones on the other instances, the change will be valid only for the particular instance.
You can still set a uniform system severity as either setting such as for the tree or equalizing the instance severities in the Per Instance Configuration tab.
Open SAP NetWeaver Administrator and choose .
Searching for Log Controllers
From the Show dropdown box, choose Logging Categories or Tracing Locations , respectively.
In the Category or Location field, enter a keyword to find the log controller(s) you need. Asterisk (*) is a valid entry.
Choose Go .
The search result displays a window with all the relevant log controllers. When you select some of them, it displays the log controller within the tree navigation.
Sophisticated Filtering
Choose Open Filter .
In the Category or Location field, enter a keyword for the log controller(s) you need.
From the Severity field, select a comparative method and the relevant severity level.
To search by a specific severity case, select an option from Severity Origin :
Persisted Configuration - shows log controllers whose severity is persisted (by you or another user)
Inherited from Parent - shows children that inherit the parent's severity which has been previously persisted
Troubleshooting Session - shows log controllers whose severity concerns an enabled debug session. This debugging task refers from the Application Manager tool in SAP NetWeaver Administrator.
Runtime Override - shows log controllers whose severity has been illegally set through SAP Logging API via an application.
In the File Name field, enter the name/part of the name of the log file.
Choose Apply Filter .
To remove the current search data, choose Clear Filter .
Changing the Severity of a Log Controller
In Logging Categories or Tracing Locations pane, from the tree structure, choose the log controller you want to configure.
From the Severity dropdown box, choose a severity level.
If you want this severity to be relevant to its children log controllers, choose Copy To Sub-Tree .
If this severity level is lower than the default one, a warning window appears.
If you want this changed reference for the children to be valid only for the current filter, choose Copy to Filtered Sub-Tree .
To find all destinations assigned to the selected log controller on system level, choose .
If you want to reset the severity of the selected log controller to its default value, choose Reset Category or Reset Location .
Choose Save Configuration .
More information:
You can see the log records of this severity configuration. To do that, choose and then, choose .
Configuring Log Controllers per Instance
Choose the Per Instance Configuration tab.
The Instance ID column now displays the ID numbers of the relevant instances for the selected controller.
From the Severity column, choose the new severity. This change will be valid for all instances on the cluster.
Select an instance.
Its details appear in the table below, displaying the destinations of the selected controller.
Restoring the Log Configuration
Select the relevant log controller.
Choose Default Configuration .
The default severity for categories is INFO, and for locations is ERROR.
Confirm your choice.