Log Configuration
Use the Log Configurator runtime service in the Visual Administrator to manage the logging and tracing configurations. You can configure the logging of J2EE components and deployed applications.

Before using the configuration options, it is advisable to read the general rules for using logs and traces in J2EE Engine.
To ease the configuration process, two configuration modes are provided – simple and advanced.
● Simple mode – for assigning severity levels to locations and categories.
● Advanced mode – for configuring logs, traces, destinations and formatters.

The advanced
mode has to be used with extreme care and only by users who are familiar in
detail with
SAP Logging
API.
To switch between
the modes, choose
To advanced mode/To simple
mode.
By default the Log Configurator service Runtime tab runs in Simple mode.
For more information, see:
Working with the Advanced Mode
The Log Configurator service provides an option for automatic archiving of log files.
1. To activate the function, choose Server → Services → Log Configurator.
2. Choose Properties tab.
3. Set the value of the ArchiveOldLogFiles as ON.
4. The ArchivesDirectory property shows where the system stores your logs.
The default value is .log/archive.

There is no automatic procedure for deleting the archives. You have to do this manually.
You can also manage the storing of system critical logs in the database.
For more information, see:
Configuring System Critical Logs
In cases, when more than one Visual Administrator is connected and works with the Log Configurator service, you are able to manage the contents.
For more information, see Parallel Work with Log Configurator Service Runtime Plug-in.
If you want to reset the entire log configuration of the cluster to its installation default settings, choose Installation Defaults.
When you choose it, a “WARNING” dialog box appears to make sure you want to proceed.
The log configuring of applications that are deployed on the J2EE Engine is done via an XML file. The Log Configurator service can extract this file if it is packed in the application EAR file. The XML must be placed in the /META-INF/ directory of the EAR.
When you have several server components, each of them can specify in an XML file the way of how logging and tracing to be configured. This XML must be packed in the <SDA_root><server|dispatcher>/descriptors/ directory of the SDA.

The XML file’s name must be exactly log-configuration.xml.
For runtime management of the logging configuration, you can also use Shell Console Administrator.
For more information, see Shell Console Administrator.