You are on page 1of 67

Inhalt

Monitoring.......................................................................................................................... 2 History Reports ................................................................................................................... 5 Managing Monitors with Monitor Browser ....................................................................... 6 Permanently Active Monitors ............................................................................................ 8 Activating and Deactivating Monitors .............................................................................. 10 Protokolldateien überwachen und anzeigen ................................................................... 11 Logging Features .............................................................................................................. 15 Log (Destination) .............................................................................................................. 18 Output File ........................................................................................................................ 19 Appendix C: Default Behavior of Certain Objects ............................................................ 21 Administrative Issues ....................................................................................................... 24 Formatter ......................................................................................................................... 25 Log Configuration ............................................................................................................. 28 Log Configuration with SAP NetWeaver Administrator ................................................... 29 GUI Config Tool................................................................................................................. 31 Connecting to a Database ................................................................................................ 32 Configuring JVM Parameters ............................................................................................ 35 Configuring Instances ....................................................................................................... 38 Adding and Removing Server Processes .......................................................................... 40 Adding Filters.................................................................................................................... 43 Configuring Shared Table ................................................................................................. 44 Modifying Service, Manager, or Application Properties .................................................. 45 Adding, Editing and Removing Log Controllers ................................................................ 49 Adding, Editing and Removing Log Destinations ............................................................. 51 Adding, Editing and Removing Log Formatters ................................................................ 53 Configuring Log Files Archiving ........................................................................................ 55 Exporting and Importing a Configuration ........................................................................ 56 Managing Secure Store Data ............................................................................................ 57 Log Viewing ...................................................................................................................... 59 Viewing Logs with the SAP Management Console ........................................................... 60 SAP Logging API ................................................................................................................ 62 LOG ..................................................................................................................................... 65

Monitoring
Die Überwachung (Monitoring) des AS-Java-Systems soll dem Administrator helfen, Ressourcenengpässe oder Probleme frühzeitig zu erkennen und gegebenenfalls einzugreifen. Mit dem SAP NetWeaver Administrator können Sie den Anwendungsserver selbst sowie die auf ihm laufenden Komponenten und Anwendungen überwachen. Sie können den Funktionsumfang Ihrer eigenen Anwendungen erweitern, indem Sie Überwachungsfunktionen hinzufügen und somit die Überwachungswerkzeuge und die Infrastruktur zur Überwachung Ihrer eigenen Anwendungen nutzen. Außerdem können Sie auf Protokolldateien von einem einzigen Standort aus zugreifen und so den zeitlichen Aufwand für die Identifikation von Fehlern und für Korrekturen reduzieren.

Lokales Monitoring Java System Reports
Zur Überwachung Ihres lokalen Systems verwenden Sie das Werkzeug Java System Reports im SAP NetWeaver Administrator. Dieses Werkzeug zur Problemerkennung und -analyse können Sie folgendermaßen verwenden:   zur Überwachung von AS-Java-Cluster und Java-Anwendungen zur Nachverfolgung der Systemleistung einer oder aller Instanzen und Cluster-Knoten eines bestimmten Java-Systems  zur Ermittlung und Analyse der Problemursachen auf einem AS Java im Falle einer eingeschränkten Systemleistung  zur Feinabstimmung für die produktive Verwendung mit dem AS Java

Die wichtigsten Informationen sind in einem Set vordefinierter Charts und Reports zusammengefasst. Außerdem können Sie Daten von jedem einzelnen Monitor im Monitoring-Baum des MonitoringBrowsers anzeigen und Ihre eigenen Reports und Charts zusammenstellen. Weitere Informationen: Java System Reports

Protokolldateien überwachen und anzeigen
Für einen stabilen und fehlerfreien Betrieb des Systems muss der Systemadministrator die Protokolle regelmäßig auf Fehlermeldungen prüfen. Wenn nötig, können Sie die Standardprotokollierungseinstellungen so neu konfigurieren, dass sie optimal zu Ihrem Szenario passen. Weitere Informationen: Protokolldateien überwachen und anzeigen Log Viewing Log Configuration

Zentrales Monitoring
Wenn Sie SAP NetWeaver Process Integration 7.1 (PI) zentral überwachen möchten, müssen Sie die zentrale SAP NetWeaver Administration für PI verwenden. Weitere Informationen zur Konfiguration und Verwendung der SAP NetWeaver Administrator für PI finden Sie unter PI-Monitoring mit dem SAP NetWeaver Administrator

Zusätzliche Überwachungsfunktionen
Bei Bedarf an bestimmten Überwachungsfunktionen bietet der SAP NetWeaver Administrator weitere Werkzeuge.  Guided Procedures Monitoring Der GP-Monitor stellt Ihnen umfassende Überwachungsfunktionen für das Guided-ProceduresSystem und die dazugehörigen Anwendungen zur Verfügung und ermöglicht Ihnen so, alle etwaigen Probleme ausfindig zu machen. Der GP-Monitor ist ein Guided-Procedures-Plug-In für den SAP NetWeaver Administrator. Weitere Informationen: Guided-Procedures-Monitor (GP-Monitor)  Open-SQL-Monitoring Wenn Open SQL für Java für den Zugriff auf die Datenbank verwendet wird, ist es wichtig, nachzuverfolgen, wie mit dem Persistenzspeicher umgegangen wird. Mit den Open-SQL-Monitoren können Sie die Durchführung von SQL-Anweisungen, den Pufferstatus von Tabellen und Katalogen sowie die Verfügbarkeit und Verwendung von Open-SQL-Datenbankverbindungen überwachen. Weitere Informationen: Open SQL Monitors  Message-Überwachung Mit Hilfe des Message-Monitoring können Sie nach Web-Service-Messages suchen, die in Ihrem System gesendet oder empfangen wurden. Sie können Messages überwachen, um den Status von Web-Service-Messages nachzuverfolgen oder um aufgetretene Fehler aufzuspüren und ihre Ursache festzustellen. Weitere Informationen: Monitoring Messages  Sequenz-Monitoring Mit Hilfe des Web Services Reliable Messaging (WS-RM) können Sie sicherstellen, dass die Kommunikation zwischen einem Service-Provider und einem Service-Customer fehlerfrei abgeschlossen wird. Sie verwenden die Analysewerkzeuge des Sequenz-Monitors zum Aufspüren solcher Fehler. Mit Hilfe des Sequenz-Monitors können Sie beispielsweise seinen Status anzeigen oder fehlerhafte Sequenzen stoppen oder erneut starten. Weitere Informationen: Sequenzen überwachen  Archivierungsmonitoring

wie viele Objekte geschrieben oder gelöscht wurden und von wem. Weitere Informationen: Java Archiving Cockpit Archiving Monitor . Hier können Sie den Fortschritt der Archivierung überwachen und Statistiken darüber anzeigen.Dieser Bereich ist Teil der Funktion des Java Archiving Cockpit.

which changes in case the values reported by the monitor exceed the predefined limits. Track the performance of one or all instances and cluster nodes of a particular Java system. History Reports provides monitoring information via monitors and reports. Activities The most important actions you can perform with History Reports are listed as follows:  Viewing and modifying the monitors in Monitor Browser For more information. Monitor Browser comprises a list of monitors in a table. . choose Availability and Performance Resource Monitoring History Reports . You can view the traffic light of each monitor. Starting History Reports To start the tool. More information: Composing Reports If you experience problems using the History Reports (for example. use the History Reports and Monitor Browser embedded functions. in the SAP NetWeaver Administrator. To monitor your AS Java. see: Managing Monitors with Monitor Browser  You can combine several monitors into your own custom report and configure the chart. state and type. you can use the quick link /nwa/java-sys-reports . where you can view their current status.History Reports Use History Reports as a problem detection and analysis tool to:     Monitor the AS Java cluster and Java applications. problems displaying monitors and reports. or lack of reported data). Perform motivated tuning for productive use with the AS Java. see Troubleshooting. Detect and analyze the causes of problems in an AS Java in a situation of reduced performance. Alternatively.

 System displays taken. . its details and description are shown in the Monitor Details and Monitor Configuration screen areas. active or inactive. If no (Alert) if data values are moved to the error level. Prerequisites Open SAP NetWeaver Administrator and then choose Availability and Performance Resource Monitoring History Reports Monitor Browser . (Warning) if data values are moved to the next alert level and some problems can occur soon. Type – shows the monitor's type. Monitoring List The monitoring list comprises all available monitors within your AS Java. You can reconfigure the threshold values if the predefined levels are not suitable for your needs.Managing Monitors with Monitor Browser Monitor Browser is available as a predefined report inside History Reports and provides runtime control for displaying monitored data. Color Thresholds The list below defines the color statuses:   System displays System displays (OK) if data is at normal level and no attention is needed. Procedure Displaying and Updating Monitor's Values When you select a monitor from Monitoring List. The monitored resources and their attributes are displayed in a table. Special measures must be data is available. You can also activate or deactivate monitors that are important for your scenarios. Status – shows the current monitor's status via color thresholds.  System displays (Inactive) if the monitor is a non-performance one and/or is not working. the monitor is not activated. Attention is needed. The table provides the following monitor details:     Name – shows the complete monitor name and location. State – shows the current monitor's state used.

Activating and Deactivating Monitors
The concept of active and inactive monitors allows you to activate only the monitors that you need and to deactivate the other ones, for improving the overall performance of the system. More information about default activated monitors: Monitors Active by Default More information: Activating and Deactivating Monitors

Configuring a Monitor
You can modify additional monitor settings, such as the monitor's description, color thresholds, data collection and so on. More information: Configuring a Monitor

Permanently Active Monitors
The following table contain all monitors with state Used. They cannot be deactivated on the server processes since they participate in History Reports.

Features
Monitors with “Used” State Monitor Monitor Type Kernel/Application Threads Pool/Usage Rate Kernel/Cluster Manager/MessageContext Communication/ General (MessageContext)/Average MS Process Time Kernel/Cluster Manager/SessionContext Communication/ General (SessionContext)/Average Session Process Time Kernel/Session Manager/Active Web Sessions Count Kernel/Session Manager/Logged-in Users Count Kernel/Session Manager/Opened EJB Sessions Count Kernel/Session Manager/Opened Security Sessions Count Kernel/Session Manager/Opened Web Sessions Count Kernel/System Threads Pool/Usage Rate Services/Http Provider/General/AllRequestsCount Services/JMS/Num of not started VPs/Not Started Virtual Providers Count Services/Keystore/System Entries Services/Keystore/User Entries Services/Log Configurator/General/TotalLogFileSize Services/Log Configurator/Messages/All Services/Log Configurator/Messages/Error Services/Log Configurator/Messages/Fatal Services/Log Configurator/Messages/Warning Services/Memory Info/Allocated Memory Services/Memory Info/Available Memory Services/Security/Aggregated Data/UnsuccessfulLogonAttemptsCount Services/Security/Data Per Application/SAP-J2EE-Engine/ UnsuccessfulLogonAttemptsCount Services/Security/Data Per Application/sap.com/com.sap.lcrsld/ UnsuccessfulLogonAttemptsCount Integer Integer Integer Integer Integer Integer Long Integer State State Long Long Long Long Long Integer Integer Long Long Long Integer Integer Integer

Monitors with “Used” State Monitor Monitor Type Services/Security/Data Per Application/sap.com/tc~dtr~enterpriseappdtr/ UnsuccessfulLogonAttemptsCount Services/Security/Data Per Application/sap.com/ tc~lm~itsam~ui~mainframe~wdwebdynpro_resources_sap.com_tc~lm~itsam~ui~ mainframe~wd/UnsuccessfulLogonAttemptsCount Services/Security/Data Per Application/service.naming/ UnsuccessfulLogonAttemptsCount Services/Security/Data Per Application/ticket/ UnsuccessfulLogonAttemptsCount Services/Timeout/EstimatedFrequencyPerMinute Services/Web Container/ AverageProcessingTime Long Long Integer Duration Long Long

2. From the Show dropdown box.Activating and Deactivating Monitors Inactive monitors have no history and do not pool data from the monitored resources automatically. since they participate in the History Reports. From the Monitor Configuration pane. 4. The relevant monitor is displayed as activated in the table. Select a monitor you want to deactivate. A table with all monitors of that kind are displayed. . 4. 2. More information: Managing Monitors with Monitor Browser Procedure Activating Monitors 1. From the Show dropdown box. Note You cannot deactivate monitors with state Used. Go again to the Show dropdown box and choose Inactive/Not used. 3. choose the Deactivate button and then choose Save. These monitors can retrieve information only on demand. Deactivation of unused monitors minimizes the impact of the monitoring service on the CPU and memory consumption. Deactivating Monitors 1. The relevant monitor is displayed as inactive in the table. A table with all monitors of that kind are displayed. More information: History Reports 3. It also reduces the monitoring history by not storing history for monitors that are rarely used. choose Inactive/Not Used. From the Monitor Configuration pane. choose the Activate button and then choose Save. Select a monitor you want to activate. Go again to the Show dropdown box and choose Active/Used. choose Active/Used. Prerequisites You have opened the Monitor Browser application.

Protokolle werden gewöhnlich in Kategorien geschrieben. die Sie festlegen können. den Archivierungsspeicherort konfigurieren und angeben. Traces werden normalerweise in Lokationen geschrieben.und Trace-Sätze enthalten Informationen über die Systemausführung. Die Standardwerte für den Schweregrad sind:   für Kategorien – INFO für Standorte – FEHLER Weitere Informationen: Log Configuration with SAP NetWeaver Administrator Speicherung von Traces konfigurieren Sie können den Speicherort für Trace-Dateien konfigurieren. Weitere Informationen: Logging Features Konfiguration Die nachfolgende Tabelle enthält Konfigurationseinstellungen. Weitere Informationen: Log Manager Archivierung ein. wenn die Standardeinstellungen nicht geeignet sind: Konfigurationsaufgabe Log-Controller-Severities konfigurieren Beschreibung Sie verwenden das Werkzeug Log Configuration im SAP NetWeaver Administrator. ausschalten Die Protokoll-und Trace-Archivierung ist standardmäßig ausgeschaltet.und Trace-Sätze von AS Java nach einem bestimmten Kriterium filtern und anzeigen. Sie können Sie einschalten.  Protokollsätze werden hauptsächlich von Administratoren für das Überwachen der Systemaktivität und dem Ausführen von Fehleranalysen verwendet. welche Dateien archiviert werden sollen. die Sie bei Bedarf durchführen können: Aufgabe Protokolle bei laufendem AS Java filtern und anzeigen Beschreibung In jeder vordefinierten Sicht oder benutzerdefinierten Sicht können Sie Protokoll. Weitere Informationen: Filtering Logs and Traces . Weitere Informationen: Configuring Log Files Archiving Aufgaben Die nachfolgende Tabelle enthält Aufgaben.Protokolldateien überwachen und anzeigen Protokoll. indem Sie den Log Manager verwenden.bzw.  Trace-Sätze werden in der Regel von Entwicklern und Servicetechnikern für das Aufzeichnen und Analysieren der Vorkommnisse von bestimmten Programmereignissen während der Laufzeit verwendet.

fangen die neuen Protokolle an./log/archive/temp extrahiert.und Trace-Dateien löschen. die alten Protokolle zu überschreiben.  Sie können manuell den Teil der Protokoll.Aufgabe Protokolle bei nicht laufendem AS Java filtern und anzeigen Protokollsätze mit Schweregrad ERROR oder FATAL anzeigen Protokolldateien löschen Beschreibung Wenn kein AS Java auf dem zu überwachenden System läuft. die erste Protokolldatei zu überschreiben.  Sie können jene temporären Protokoll. Wenn Sie Archive von Protokollen und Traces öffnen. um Plattenplatz freizumachen. Wenn Sie die Archivierung aktivieren.und Trace-Dateien regelmäßig löschen. wenn Sie Archive mit Hilfe des Log Viewer anzeigen. Beim nächsten Mal werden die Archive daher schneller angezeigt. Sie können Protokolldateien auf drei Arten löschen:  Automatisch – Wenn die Protokolle die Größe von fünf Dateien mit jeweils 10 MB erreichen. . die vom System generiert werden. werden die Protokoll. Die Protokoll.und Trace-Sätze mit Schweregrad ERROR oder FATAL herausfiltern und anzeigen. Achtung In einigen Ländern ist das Erstellen von Sicherungskopien der Sicherheitsprotokolle per Gesetz vorgeschrieben. die somit automatisch gelöscht werden.und Trace-Sätze mithilfe eines entfernten Log Viewer filtern und anzeigen. den Sie nicht benötigen – z. Weitere Informationen: Connecting to a Remote System Um die SAP NetWeaver-Systemlandschaft auf kritische Zustände hin in jeder beliebigen vordefinierten oder benutzerspezifischen Sicht zu überwachen.und Trace-Dateien werden anschließend nicht aus diesem temporären Verzeichnis gelöscht. können Sie nur die Protokoll. Empfehlung Sie sollten diese Protokoll.oder Trace-Dateien löschen. Aus diesem Grund müssen Sie regelmäßig Sicherungskopien von Ihren Sicherheitsprotokolldateien anfertigen und aufbewahren. die Standard-Traces.B.und Trace-Dateien jedes Archivs in das temporäre Unterverzeichnis . erstellt das System eine Sicherungskopie im ZIP-Format vom Set der fünf Dateien und fängt an. können Sie Protokoll.

und die Archivierungsgröße. Sie können zur Überwachung und Anzeige von Protokollen auch die folgenden Werkzeuge benutzen:   Log Viewing with the SAP MC Command Console Log Viewer Weitere Informationen Im Verzeichnis <SAP_Installationsverzeichnisr>\<Systemname>\<Instanzname>\j2ee\cl uster\<Servername>\log finden Sie folgende Protokolle: \system\database.log \system\server.log \system\configchanges.Aufgabe Größe von Protokollund Trace-Dateien überwachen Beschreibung Es gibt zwei Arten der Überwachung für Protokolle und Traces – für die Datei. wenn die Überwachungsampel von gelb auf grün wechselt.log \system\userinterface. Weitere Informationen:Monitor Browser Werkzeuge Mit dem Werkzeug Log Viewer in SAP NetWeaver Administrator können Sie alle als Liste oder Text formatierten Protokolle und Traces anzeigen.log Zusätzlich stehen die folgenden speziellen AS-Java-Log-Controller zur Verfügung: AS-Java-Komponente AS Java allgemein Business Process Management Protokoll-Kategorie Trace-Lokation /System /Applications/BPM com. den Wert.log \application. Verwenden Sie dafür den Monitor Browser in SAP NetWeaver Administrator.log \system\security.glx /Runtime . Weitere Informationen: Log Configurator Sie können auch die Einstellungen der Überwachungsampel ändern – z.log \system\logging.sap.B. die innerhalb der gesamten SAP NetWeaverSystemlandschaft erzeugt werden.

com.prt. 3. 4.portal.sap.sap.ivs.eu.sap.sap. Probleme bei der Darstellung von Seiten /Server /System/Server com. com.pb Zusammensetzung von Services /Applications Visual Composer Web-Services com.sapj2ee com.vc.admin.sap.portal.fpn com.sap. Probleme beim Anlegen von Content mit XMLScripts (Generic Creator) 6.server05 /Server /System/Server/WS com.portal.sap.gp.connectors com.configurati on Guided Procedures Portal 1.OBN com. 5.engine.webservice s .sap. Probleme in der Administrationsumgebung 2.rt* com.sapportals.services.* 1. Probleme beim Deployment von Content 8.sap.runtime. com.rt com.genericCrea tor 6. Probleme bei Berechtigungen/Sicherheit 7.ui com.portal. com.portal.caf.sap.portal.AS-Java-Komponente Composite Application Framework Protokoll-Kategorie Trace-Lokation /Applications com.portal. Probleme bei Portalen im Verbund 5.sap.sa.sap.sap.caf com.caf.portal. Probleme bei der Portalanbindung 4.sap. 8.sap.adminstudio com.sap.sap.adminstud io 2.portal.caf.portal.security 7. Probleme bei der objektbasierten Navigation (OBN) 3.caf.pcd com.ui.

Traces can be switched on if a problem has occurred and a detailed analysis of a distinct part of a program is necessary. Log records provide the following common information:        a short descriptive message a timestamp of the event the source of the record the log controller a severity. system and instance name the server process Log files are used by system administrators to identify problems in system operations. The Log Manager is part of the Java Enterprise Runtime and is the first manager to be started at system startup. Tracing Tracing is a process of writing detailed information about an operation to an output file. you can reconfigure the default system log archiving and tracing behavior. logs are always switched on and get written automatically.Logging Features The following main features help you to manage your logging functionality and activities. specifying the importance of the record the host. Features Logging Logging is a process of creating and storing permanent records of events that can be reviewed. They have predefined granularity (severity) that can be modified during runtime. tracing is normally turned off. . Using the Log Manager properties. printed and analyzed. Therefore. Therefore. Log Manager Log Manager is a module that manages the process of logging system events. Trace records provide the following:   a detailed sequence of statements that describe the events of an operation as they are executed diagnosing of an abnormal condition Trace files are used by support engineers and developers.

Two types of log controllers are available:  Category — describes messages specific to distinguished problem areas. networking. It is used to emit log messages. It is used to emit trace messages.  namespace – this is equal of <prefix + range>. It is a Java object that manages the writing of log and trace messages. you need a log controller. also known as logs. WARNING – The application can recover from an anomaly and fulfill the required task. that is.  Location — describes messages that originate from delimited source code areas. Message ID Message ID is a unique identifier assigned to each log/trace message. range – a two-symboled combination that consists of number and lowercase Latin alphabet characters. with extensive and low level information. Each log destination type can print messages in the following formats: TraceFormatter. Destinations are predefined by the SAP Logging API. Typical problem areas are: databases. but needs attention from a developer/operator. More information: Log (Destination) and Formatter Levels of Severity An important part of any log and trace message is its severity.  ERROR – The application can recover from an error. XMLFormatter. Note Log controllers are also identified with certain severity. only data of a defined severity is collected. mostly for announcing what has been performed. security auditing. but it cannot fulfill the required task due to the error. Logs and traces can be limited to certain severity levels. It is unique for each Message ID. A Message ID represents the following string: [prefix] : [range] [number]. where:   prefix – a meaningful word or abbreviation concerning an AS Java component.  FATAL – The application cannot recover from an error. Log and trace messages are written in destinations. too. and ListFormatter. INFO – Informational text. The increasing order of the severity levels is:     DEBUG – For debugging purpose. It denotes the level of importance or relevance of a certain message. and others. generated in the AS Java.Control of the Output To control the log output. and the situation causes fatal termination. The uniqueness of the concept do not allow two logs/traces to have one and the same Message ID assigned. PATH – For tracing the execution flow. .

More information: Log Configuration  View all available logs and traces in AS Java. you can:  Configure log controllers. More information: SAP Logging API  Perform some advanced logging tasks by using the LOG group of shell commands. use the SAP Logging API. number – a number from 0 to 9999 with leading 0s. Each Message ID has unique number in the range. destinations and formatters. More information: How to Write Log and Trace Messages  Enable the logging and the output messages of your application. More information: LOG . The first number is ‗0000‘ and the last possible number in a range is ‗9999‘. Activities Using logging functionality. More information: Log Viewing  Develop logging for your own applications using the SAP NetWeaver Developer Studio. To do this.

io.directs the messages to the System. They have logs assigned to them according to the default configuration instead.directs the messages to an arbitrary OutputStream (java. Currently. there are some log controllers that do not inherit from their parents. but to write to their own specific destinations.NONE).OutputStream). the following logs are predefined:  ConsoleLog . Unlike the default for log controller (Severity. a severity level can be defined for each log. Activities   Commonly. all the possibilities to change the severity of a log have been removed.ALL. The main reason for this is security.err (java. in the log configuration. However. More information: Output File.lang. That is. Therefore.System). the default for a log is Severity.Log (Destination) A log represents the destination where the messages are written.  FileLog . currently user can consider logs as they have no severity at all. .trc file (which is considered public).  StreamLog . This log type is typically used in the debugging process for a quick overview of problems. log controllers inherit the logs from their parent controllers. there is no effect on the main severity level check with the log controller. Like the log controller. The purpose of those log controllers is not to write their messages to the defaultTrace. Note To avoid confusion.directs the messages to a file or a set of rotating files.

log == ""C:/temp/trace. By default.log". More information: Appendix C: Default Behavior of Certain Objects. %u A number that makes the file name unique.0. this is appended to the end of the filename/file pattern specified. This is useful only when you specify the file size limit and the maximum number count to do rotation. %g The sequence number of the file. %h %t Home directory.%g.log" / Local file name separator. In the SAP Logging API. The value of the system property:"user. it is "C:\temp".log" To avoid file naming conflicts. There are a number of options you can use to configure the behavior of an output file. System temporary directory. messages written to an output file are in the ListFormatter. There is only one single output file that constantly increases in size.log " "C:\temp\trace. This section explains certain common configuration features to complement the JavaDocs. Normally. By default.home" The value of the system property: java. without using any special character encoding. this is done by assigning FileLog to your source objects. Therefore:"C:\temp\trace. Placeholder Description Comments "C:\temp\trace.io. . %% The percentage sign. such as the filename separator. using the SAP Logging API:    Filename Limit file size and do sequencing on the output file Choose FileLog or physical file Features Filename The filename can be expressed as a full file path or in a pattern with a number of available placeholders.tmpdir"".Output File Directing messages into a file is a very common practice. This can help the potential "hardcoding" problem and platform dependent issues. For example: "%t/trace.log" == "%t/trace.

If do so. one – with TraceFormatter and another – with XMLFormatter.limit log[File]. you can manipulate the output behavior of the output file through the API of the FileLog. With the several configuration options mentioned in the previous section. 10.9. 4. FileLog _file = new FileLog("%t/trace.log".formatter = = = = = FileLog %t/trace.1. depending on the option you use to do the configuration. or both have values equal to zero. For example. new TraceFormatter()). 3. In case of the configuration file.log" (count = 10). 1:1 Recommended The FileLog and the actual output file must be in a 1:1 relationship. Then the next file to be written will be again in " C:\temp\trace.000 bytes). Recommendation We recommend that you do not create two instances of the FileLog on the same file with different configuration.0. 2.%g.log 800000 10 TraceFormatter The first output file is created in the "C:\temp\trace. Otherwise.%g. FileLog or Physical File FileLog is a logical representation of a physical output file where messages are directed.cnt log[File]. Syntax 1. you may not synchronize the messages in a multi-threading environment correctly. More information: Administrative Issues. 800000. The full message text may be interrupted and interwoven with another message text.log".log" (sequence number starts with '0' ) and when its size exceeds the limit (800. log[File] log[File]. This process continues to the last sequenced file "C:\temp\trace.Output File Sequence and Rotation This is done implicitly when you specify values for the file size (in bytes) and the cap for the sequencing count. You can also do assignments of the FileLog to source objects. or "best guess" values are used (through the configuration file). 5. before rotating back to the first file. either an exception can be thrown (through the API). For example. This pair of parameters must coexist together either they both have values assigned. This can be done when the FileLog constructor is called. both attributes get default zero values.pattern log[File]. . the next incoming message will be directed to a new file – "C:\temp\trace. the syntax is: Syntax 1.0.log".

ALL <none> TraceFormatter ListFormatter 0 No further filtering.NONE ty <output logs> <filters> Log Severity <filters> ConsoleLog FileLog Formatter Formatter Limit No ceiling restriction: output nothing.fooMethod [main] Fatal: A sample fatal message ListFormatter Pattern Example: #1. 2001 10:10:00 PM com.165:4A5AB2:E99D42D4F4:8000# Mon Jan 01 22:00:00 PDT 2001# com. No rotating set of numbered files.Appendix C: Default Behavior of Certain Objects Default Attributes Values Class Attribute Default Value Description No output at all.FooClass.48. No floor restriction: output all. Do not further suppress messages. Count TraceFormatt Pattern er 0 %24d %-40l [%t] %s: %m Log file name generated without a sequence number.FooClass. LogController Severity Severity.sapmarkets. No further filtering.sapmarkets.3#10. fooMethod#main##0#0# Fatal##Plain###A sample fatal message# . <none> Severity.NONE MinSeverit Severity. No file size limit. <none> No output at all. Example: Jan 01. 'Count' must == 0.sapmarkets.FooClass# com.ALL y MaxSeveri Severity.27.

time. <source>com. severity.48. <id>10. args?)><!ELEMENT id e> <location>com. thread.fooM ethod </location> <thread>main</thread> <severity>Fatal</severity> <msg- (#PCDATA)><!ELEME type>Plain</msg-type> <msg-clear>A NT time sample fatal message</msg-clear> (#PCDATA)><!ELEME </record> NT source (#PCDATA)><!ELEME NT severity (#PCDATA)><!ELEME NT location (#PCDATA)><!ELEME NT thread (#PCDATA)><!ELEME NT msg-type (#PCDATA)><!ELEME NT msg-code (#PCDATA)><!ELEME NT bundle (#PCDATA)><!ELEME NT msg-clear (#PCDATA)><!ELEME NT args (arg+)><!ELEMENT arg (#PCDATA)> Highlights of Default Behavior Class Property Default Value Description .FooClass</sourc msg-type. msgcode?.165:4A5AB2:E99D2EDAFF: 8000</id> <time>Mon Jan 01 22:00:00 PDT 2001 </time> location.sapmarkets.27.sapmarkets.Class Attribute Default Value Description Example: XMLFormatte Pattern r <!ELEMENT log (record*)><!ELEME <record> NT table (id. source. msg-clear?.FooClass. bundle?.

0. Both MsgCode & MsgClear available. Only when explicit configuration is done on relative 'A'.Class Location Property root name Default Value Description Empty string. delimited by "/". if not specified by user %t/trace. Optional Both MsgCode & MsgClear available.log Trace Filename.log. up to the viewer.log . Nothing is output by relative 'A'.cnt.log For example.<ext> For example: trace. Full name should be hierarchical. "" Category root name "/" Similar to root directory. delimited by ". with size limit and count <filename>. Relative 'A' unaffected. the output is generated by it. up to the viewer. and still has default Severity. C:\temp\trace.NONE and no output destination.1. FileLog Filename. Optional provided by users explicitly in 'MsgClear'. trace. TraceFormatter Message displayed Content of 'MsgClear' in Either translated text in 'MsgClear' or text any case. Full name should be hierarchical." . ListFormatter Message displayed XMLFormatter Message displayed Location or Category with relative 'A' OutputBehavior by relative .

if this happens. the errors occurring within the logging framework have to be thrown and caught appropriately. lead to an immediate program termination when the class is loaded. These can be rectified internally and a message can be logged to indicate the problem without terminating the program. The default setting for FileLog is used. Therefore. It must not disturb the running application. There are several ways for replacing the incorrect value with the best-guess value:  Using the default value. it is stored temporarily and can be retrieved by the caller through the getException() and throwException() methods. o A message string or message code must not be a null string. The exception is not lost.Administrative Issues Error Handling Mechanism The error handling mechanism must be done carefully in the logging tool. More information: Appendix C: Default Behavior of Certain Objects. called in static field declarations and initializers. wrong resource bundle information. That is. meaningless null message string. o When a message code cannot be resolved to a localized string. o If a spelling error occurs when defining a Log or Formatter. Ignoring it.   Estimating the closest value. Examples Some of the potential mistakes are: invalid severity definition. limit and cnt are both equal to zero. poor configuration. the value of the message code is used directly. a constant <null> is assigned. Workaround The approach is to tolerate the exception and to correct the error. the value is ignored and nothing is assigned. However. The program then continues to run. Example For example: o Invalid configuration for FileLog for the pair of parameters limit and cnt. and so on. Exceptions generated from methods. .

and ListFormatter. 2007 10:10:00 PM com.FooClass.  The default pattern: %24d %-40l [%t] %s: %m The corresponding output is: Jan 01.Formatter Each log destination type can print messages in different formats: TraceFormatter. In the second example: ―%l‖ displays the full string that will be left-aligned. the string will be truncated. %t %s %m %I %p %g The thread that emits the message.fooMethod) that will be right-aligned (with a minus sign).FooClass. For example. The formatted message text. The time stamp in milliseconds (for example.fooMethod). . The group identification.FooClass. If the length of a string exceeds the defined width.sapmarkets. the corresponding output is: Jan 01. 1970 00:00:00 GMT).sapmarkets. The log controller through which the message is issued (for example.sapmarkets.FooClass). com.FooClass.fooMethod [main] Fatal: A sample fatal message. Features TraceFormatter   A human readable format. The table below describes the meaning of the placeholders: Placeholder Description %d %l %c Timestamp in readable form. XMLFormatter. since January 1.  The number in the pattern denotes the width of a field.sapmarkets. The message severity. com. 2001 10:10:00 PM com. The most commonly used formatter when you want to understand quickly what is happening with the application. The Message ID.sapmarkets. The location of origin (for example. In the first example: ―%-40l‖ indicates a limit of 40 chars for the location name (com. if the pattern becomes %24d %l [%s] %m.fooMethod [Fatal] A sample fatal message.

instead of being read directly by the user. That is. thread. severity. level. <!ELEMENT level (#PCDATA)> 9. args?)> 2. <time>Mon Jan 01 22:00:00 PDT 2001</time> 4.ID543210#  The order of the fields. Syntax 1. <!ELEMENT msg-type (#PCDATA)> 14. <location>com.sapmarkets.48. <record> 2. <!ELEMENT table (id. <thread>main</thread> 7. More information: Log Viewer  Sample output of the same result is: #2.XMLFormatter Suitable for file transfer to be further processed in other applications. <id>10. location.5.FooClass</source> 5. <!ELEMENT time (#PCDATA)> 4. time. <!ELEMENT group (id.main]#Plain## Number of debug nodes was changed from 1 to 1 for Instance .sapmarkets. delimited by the hash sign is: o o o Version (of the ListFormatter) Message ID Timestamp .FooClass. <!ELEMENT relative (#PCDATA)> 13. <!ELEMENT indent (#PCDATA)> 10. msg-type. <!ELEMENT location (#PCDATA)> 6. <!ELEMENT msg-clear (#PCDATA)> 17. </record> The DTD of the result is: Syntax 1.27. <!ELEMENT severity (#PCDATA)> 11. relatives?.  Simple hash-separated fields to be processed mainly with the Log Viewer. group?. msg-code?. <severity>Fatal</severity> 8.0#2008 04 15 18:47:29:778#+0300#Info#/System/Changes/configtool# ###C0000A37462200020000000201BE2893###configtool########Thread[Thread-6. <source>com. <!ELEMENT msg-code (#PCDATA)> 15. <!ELEMENT relatives (relative+)> 12. msg-clear?. <msg-clear>A sample fatal message</msg-clear> 10. <!ELEMENT bundle (#PCDATA)> 16. <!ELEMENT id (#PCDATA)> 3. <!ELEMENT args (arg+)> 18. <!ELEMENT thread (#PCDATA)> 7. bundle?. <msg-type>Plain</msg-type> 9. source.fooMethod</location> 6. it sends the data for further processing by another application. <!ELEMENT arg (#PCDATA)> ListFormatter  The output of this format serves like a router. <!ELEMENT source (#PCDATA)> 5.165:4A5AB2:E99D2EDAFF:-8000</id> 3. indent)> 8.

o o o o o o o o o o o Source name (log controller) Thread ID Location name (the actual code location that generates the message) Group indentation Message severity Message Type (PLAIN or JAVA) Message Code ResourceBundle name Message Number of arguments Arguments .

More information: Log Configuration with Config Tool  Activating or deactivating log files archiving More information: Configuring Log Files Archiving  Performing advanced log configuration tasks using the LOG group of shell commands. using the following methods:  Configuring the severity of log controllers on a system or a certain instance level at runtime More information: Log Configuration with SAP NetWeaver Administrator  Performing advanced log configuration tasks. More information: LOG . configuring log formatters. and so on. adding log destinations. such as creating log controllers.Log Configuration You can perform log configuration activities.

they are organized along code packages. To access the tool. Note The configuration steps for both logging categories and tracing locations are the same. In SAP NetWeaver Administrator. and others. Controller with such a severity logs all the messages regardless of their severity. . networking. In SAP NetWeaver Administrator. You can alternatively use the quick link: http://<host>:<port>/nwa/log-config. locations are named as tracing locations. the steps in the configuration procedures treat them as a whole. It is used to store and emit trace messages. categories are named as logging categories. security auditing. Typical problem areas are: databases. Since trace messages are meant for developers and support engineers. Therefore. open SAP NetWeaver Administrator and then choose Troubleshooting Logs and Traces Log Configuration . with extensive and low level information. More information: Log Viewer Features Log Controllers Log controllers are objects that manage the writing of log and trace messages. Severity levels The severity denotes the level of importance or relevance of a certain message. It is used to store and emit log messages. Two types of log controllers are available:  Location – describes messages that originate from delimited source code areas. Integration If you want to view the logs and traces of your AS Java.  Category – describes messages specific to distinguished problem areas.  DEBUG – For debugging purpose. The increasing order of the severity levels is:  ALL – The lowest severity.Log Configuration with SAP NetWeaver Administrator Log Configuration provides options for online configuring the severities of log controllers in the whole system or in a certain system instance. choose Relative Links Log Viewer .

Activities Configuring Log Controllers .  FATAL – Announces that the application cannot recover from an error. For example.  NONE – The highest severity. looping and branching operations and so on. and the situation causes fatal termination.   INFO – Informational text. WARNING – Announces that the application can recover from an anomaly and fulfill the required task. but needs attention from a developer/operator. but it cannot fulfill the required task due to the error. PATH – For tracing the execution flow. Log controllers with such a severity suppress all the messages logged into them. entering and leaving a method.  ERROR – Announces that the application can recover from an error. except for the messages with the same severity. mostly for announcing what has already been performed.

To start GUI Config Tool. Manager or Application Properties Log Configuration with Config Tool Configuring Log Files Archiving Activating a Configuration Template Exporting and Importing a Configuration Managing Secure Store Data . Features The following are the advantage tasks you can do using the GUI Config Tool (in comparison with the command console Config Tool):      Change the configuration template Make log configuration Manage the secure store data Search for properties in Config Tool Add filters Activities Here is a list of all the tasks available for GUI Config Tool:             Connecting to a Database Configuring JVM Parameters Configuring Instances Adding and Removing Server Processes Adding Filters Configuring Shared Table Modifying Service. double-click the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. You can use simple and expert mode for configurations.GUI Config Tool Use the GUI Config Tool to offline configure AS Java via graphical UI.

System Name Displays the name of the system to which this data applies. next time you start the Config Tool. choose "Yes" if you want to connect to the default database. Secure Store Key File Contains the path to the secure store key file. Note If you check the "Do not ask me again" indicator. start the Config Tool.properties C:\usr\sap\LKG\SYS\global\security\data\SecStore . it will automatically connect to the default database.Connecting to a Database This procedure enables you to connect to a remote database and display an installed AS Java configuration. In the Connection settings dialog window.properties file from the configtool directory. Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. 3. Procedure 1. you can remove the config. This file is encrypted for security reasons. In the Connect dialog window. Then. The default database connection is via the Secure Store. or "No" to connect to a different one. To connect to a different database. 2. Connecting Settings Secure Store Settings Secure Store File Contains the path to the secure store properties file.key LKG . The key file contains the password for the encrypted store file. choose whether to connect via secure store or via direct login and enter the required data in the relevant fields. Description Example C:\usr\sap\LKG\SYS\global\security\data\SecStore .

C:\usr\sap\LKG\SYS\global\security\lib\tools\iai k_jsse.jar General Settings Description Example . RDBMS user Specifies the user name for this database connection. Description Example jdbc:sapdb://sofD60163517A/CE1?timeout=0&spaceop tion=true&unicode=true com. IAIK Library Specifies the IAIK JAR files directory. RDBMS password Specifies the password set during the installation of the relevant AS Java. connection settings. by which jdbc/pool/LKG Connectio the value contains the DB ns Direct Login Settings RDBMS URL Specifies the URL for the database connection in the correct format for the corresponding driver.Secure Store Lib Specifies the security directory. C:\usr\sap\LKG\SYS\global\security\lib\tools\iai k_smime.DriverSapDB SAPLKGDB . C:\usr\sap\LKG\SYS\global\security\lib RDBMS A property key. C:\usr\sap\LKG\SYS\global\security\lib\tools\iai k_ssl. It contains IAIK JAR files you need to use to open the Secure Store. It enables the encrypting and decrypting of the properties file.C:\usr\sap\LKG\SYS\global\security\lib\tools\ia ik_jce.sap.jar.dbtech.jar.jar. Driver name Specifies the class name of the JDBC driver to be used for database connections.jdbc.

properties. Then. Choose Save Connection As. View Startup Options . .properties‖ file to connect to a database. for example user. Then. open the visual. add the line: show. C:\\sapdb\programs\runtime\jar\sapdbc. Enter a file name with the extension ―. in the configtool folder. choose Startup Options. check Show connection dialog. choose dialog box. start the Config Tool. 2. Then.  Open a previously saved ―. .properties file for text editing. Choose Save.properties file. Result You have successfully connected to a database.RDBMS Driver Location RDBMS Initial Contains the path to the RDBMS driver.jar Specifies the number of database connections to 1 Connectio be created initially in the ns RDBMS Maximum connection pool. This is necessary for the system to provide a better performance of the GUI Config Tool when you work with instances.indicator=YES. Then. in the dialog window. check Use loading indicator.loading. Choose Connect to DB. Save the connection properties you have just set as following: 1. in the Note If you are not available to proceed this via the GUI tool. Choose Load Connection Settings. 3. you have the following options:   Directly connect to the relevant database. After filling in the connection fields. After opening the GUI Config Tool. Specifies the maximum number of database 10 Connectio connections to be kept in ns the connection pool. you can proceed the following steps for better future use:  If you want the Connection settings dialog box to appear again on startup.properties‖.  If you use a Linux or Unix operating system. View The other way is to delete the visual.

Caution Avoid editing properties which values are not static (link values). 5. 6. Choose the template or the instance you want to configure. In Custom property data. Procedure Configuring JVM Environment Properties 1. you can enter a new value for the property. Note You cannot delete default or inherited properties but only custom ones. such as DebugPort and ClassPath. When you select the property. If you want your settings to be valid for all instances. restart AS Java. 2. if a property has a link value (formula). Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. 7. you can see the default value of the property. The JVM is used for running the AS Java and all deployed applications. Choose View Expert Mode . Select VM Environment. choose Restore to Default Value. 2. 9. In Default/Inherited Property Data. Choose Set Custom Value. 3. The template configuration is valid for those instances that do not have custom configuration. you can see its default link value in the Inherited Value field. Choose (Apply Changes). 4. make the configurations on a template level. 8. You can change values in the configuration template or for a specific instance. In order the changes to take effect. . Select a property from the table below. Configuring JVM Parameters on Template Level 1. If you want to retrieve the default value of the property. in the table its calculated value is displayed. Select the template. All the properties on an instance level are shown with their calculated values.Configuring JVM Parameters This procedure enables you to view and edit the Java Virtual Machine (JVM) parameters using Config Tool. That is.

3. enter the new value.dir=C:/Mydir". 5. Select VM Parameters. . 6. we recommend that you change only the maxHeapSize. the AS Java will experience problems and may restart. 7. choose the parameter and then select Enable/Disable. If you enter a value that is too low. verbose:gc). To change the value of a property. Recommendation We recommend that you use sap vendor on all supported platforms. DmyKey=myValue). By default. For example: Example key="-agentlib:myagent" value="port=12345. o Additional – any additional parameters. The actual parameters used by a running JVM can be found in the development trace file of the corresponding server process. Via the following tabs you can configure the relevant template properties: o Memory – JVM memory settings. o JVM perm size If you enter an illegal value (for example. To add JVM parameters. you can make configuration changes that are specific for the selected JVM. choose New. o JVM heap size Recommendation If you want to increase the JVM heap size. 4. The changes made in GLOBAL vendor apply to all vendors and platforms. the AS Java will not start. supported by the JVM (for example. To enable/disable a parameter from the Custom Parameters table. The Config Tool automatically adds D to all newly-entered parameters. all properties are enabled. The property is added to Custom parameters. choose New. 8. In VM Type. Enter the required memory value (in megabytes) in the Custom value field. These changes apply only if the current platform and vendor matches. select it from the table and in the Custom value field.dir=C:/Mydir" This results in parameter: "-agentlib:myagent=port=12345. the value is not a number). o System – all system properties usually specified with -Dxx=yy (for example. If you want to add a custom property.

Configuring JVM Parameters on Instance Level 1. Enter the new value in the Custom Value field. In order the changes to take effect. 6. choose Additional o o o Select a VM parameter from the list. choose the relevant parameter. choose System. 11. Select VM Parameters. Optional: enter a value if the Value field is available Predefined description appears automatically. 7. Optional: enter a value and description. 4. to use a different ―vendor-platform‖ combination). If you want to retrieve the default value of the property. 5. 2. It is not possible to add new memory VM parameters but only system and custom ones. Choose the instance you want to configure. To enable/disable a parameter from the Custom Parameters table. 10. Adding New JVM Parameters 1. You can change or delete it. choose the parameter and then select Enable/Disable. restart AS Java.9. choose Restore to Default Value. choose 2. 9. Choose (Apply Changes). Choose (Apply Changes). View Expert Mode . 3. Note To add VM parameters on a template level. . To add a system parameter. Note For more advanced tasks (for example. 7. 4. 3. Choose the template or the instance you want to configure. restart AS Java. 8. Choose the VM Parameters tab. In order the changes to take effect. From the table below. choose View Expert Mode and then go to VM Type. restart AS Java. The new VM parameter appears in the Custom Parameters table. Choose (Apply Changes). Choose Set. In order the changes to take effect. Choose Set. 6. To add a custom parameter. 5. o o Enter a name as required.

Procedure Adding and Removing a Server Process More Information: Adding and Removing Server Processes Viewing and Editing the JVM Settings for a Specific Instance More information: Configuring JVM Parameters Enabling and Disabling an Instance 1. In Custom value. If you change the properties of an instance. In order the change to take effect. enter false.Configuring Instances This procedure enables you to manage Java instances. set the value of the Execute property to true. 2. 2. or view and edit the JVM settings. the changes apply only to this instance. Its function is to automatically start the specified instance during runtime of AS Java. select the instance you want to configure. From the tree structure. 4. 6. From the tree structure. To run an instance that has been stopped. 5. Choose (Apply Changes). select the instance you want to configure. Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. . restart the AS Java. disable instances. Choose VM Environment Custom value . DebugMode – specifies whether the instance is in debug mode and if the debug port is open. The value is set to true by default. 3. Enter the new value of the following settings: o o Debuggable – the debug mode feature for the selected instance is enabled. Viewing or Editing the Debug Properties for an Instance 1. Select the Execute property. 3. You can add and remove server processes. Select VM Environment.

you also need to start the message-driven beans on another server process. For example. Choose (Apply Changes). o LoadBalanceRestricted – specifies whether the instance is part of the load balancing system. first make sure you have stopped all message-driven beans running on that instance. select the instance you want to configure. 2. Select the Instance Profile tab and see information such as system name. The default value depends on the instance number and server process index number. the debug port is 50026 for server0. . operation system name. Note In case. o DebugPort – specifies the JVM debug port. and so on. 4. instance name. From the tree structure. instance number. Viewing Instance Profile Constants 1. if the instance number is 00. your applications contain message-driven beans whose destination type is Topic.Note When you enable debug mode for an instance.

More information: Enabling Debugging If you need to add more server processes to an existing Java instance. you will still be able to monitor how your application/components behave in a cluster. you can do that manually using the Config Tool.  Java instance level If you specify a number of server processes for a particular Java instance. this debuggable server process will not be operational in order to reduce the system resources consumption. You can configure the number of server processes on two levels:  template level If you define a number of server processes on a template level. the number will be relevant for all Java instances in the cluster. This means that when you start AS Java. . The debug server process is not included in the load balancing so end users will not experience stale requests (due to debugger breakpoints). the number will be relevant only for this particular Java instance. you can start this server process using the SAP MC and connect to it with debugger. inspect data and evaluate expressions. you can allocate one of them for debugging. This enables optimal utilization of the hardware resources and of the capacity of the ICM to handle multiple server processes. However. Note When planning the number of server processes you want to have in an AS Java instance.Adding and Removing Server Processes The installation procedure configures the optimal number of server processes in an instance based on the available hardware resources. When a problem appears in AS Java.

choose the template or a Java instance according to the level you want to make configurations. 5. 3. 2.Prerequisites   You have installed the basic components of the cluster. 4. In the Custom Number of Server Processes field. Note This option is available at instance level only. Make sure the AS Java is stopped. Choose Check Value to verify that your server is capable of handling the number of server processes you entered. enter the number of server processes you want to have. More information: Starting and Stopping Systems and Instances. From the tree-structure. . Correct the value if necessary. Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. Procedure 1. Choose the Servers tab.

7. For more information. see the NOTE paragraph at the beginning of this page. Choose (Apply Changes). Choose Set. 9. restart AS Java. If you want a server process (in a particular instance) to be debuggable. then the Check Value option calculates the formula and displays the value. 8. select the Debug a Server Process checkbox. Note You can set only one node for debugging in an instance. . 6.If the template configuration allows you to enter a formula instead of an exact value. In order the changes to take effect.

library. the filters apply to all instances. Choose (Apply Changes). 3. Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. Select Filters. If you set filters for a particular instance. for which you want to add filters. . If you set action filters on configuration template level. enter the name of the component. only this instance will have the filters applied. 7. Select the type of component: service. 4.Adding Filters A filter enables you to start. or disable services. application. Procedure 1. In Custom rules pane. or all components. Choose View Expert Mode . In the table with custom actions. 8. From Component Name Mask. Part of the name is a valid string. You can add filters and also edit or delete already created filters. Choose Add. The action is added to the Custom rules table. stop. 2. or disable. A table of default actions for particular components is displayed. 5. 10. select what action should be performed: start. Note You can use the asterisk sign (*) to replace part of the name or the question mark (?) to replace a single letter. enter the vendor of the component. stop. select the added entry and choose Set. 6. 11. 9. From Vendor Mask. libraries and applications. Choose the configuration template or the relevant instance.

6. EJB sessions and so on. 4. 7. 2. 3. That helps in case the AS Java is updated to apply the updates to all instances. enter the new custom value. restart the cluster. In order the changes to take effect. From the tree structure. Choose Set Custom Value. They are represented as tables in the SAP Management Console. Note If you change the properties of an instance. browser sessions. EJBs and so on. You can configure this shared table via particular properties. Web sessions. For example. Select the property you want to configure. 9. 5. 8. you can change the number of concurrently supported active Java applications. Choose (Apply Changes). Recommendation We recommend that you make this configurations on a template level.Configuring Shared Table The shared table of an Java instance stores monitoring information about applications. Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. Java processes. the changes applies only to this instance. threads. In the Custom Property Data field. . Choose View Expert Mode. Procedure 1. This procedure enables you to change the number of the relevant table's rows. Choose Shared Table tab. processes. choose the template or an instance.

  You can overwrite instance properties values with template ones. computed. Manager. then it is displayed. Features  The properties can be defined with additional parameters. if you set a custom value on a template level. Particular services and managers may have another feature – nested properties. The children properties are separated by a slash (/). That is. The properties in an instance configuration are divided in two sections:  Inherited property data Displays the template default value of a property.Modifying Service. such as type. manager.  Custom property data Displays all custom settings of a property in an instance.  Custom property data If you want to add custom values for a property. or application. More information: Basic Features of the Config Tool. and then set a different value for the same property in a particular instance. or Application Properties This procedure enables you to change the properties of a particular service. Otherwise. Note You can view and modify nested properties in Expert Mode only. manager or an application. When you select a service. and link. If there is a template custom value. . these settings are valid for all instances. using the Config Tool. the template default value is displayed. These settings cannot be changed. parameterized. If you make this change on a template level. its relevant property keys and values are displayed in a table on the right. they are displayed in the Custom property data field. range. then the instance configuration is considered. The properties in the template configuration are divided into two sections:  Default property data Displays default template configuration settings for a manager or service. Note The instance configuration has priority over the template configuration.

enter a new value. 3. Select the relevant service or manager that contains nested properties. 2. o In the Name field. The ―children properties‖ are separated by a slash (/). enter the relevant string. 5. enter a new value. respectively. Select the property whose value you want to restore. 4. 2. To set another value for the property. enter the new value. Choose Restore to Default Value or Restore to Inherited Value. Open an instance configuration. Choose Set Custom Value. 2. 3. Choose View Expert Mode . choose New. 3. Choose (Apply Changes).Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. In Custom value. Choose Set Custom Value. The custom value is restored to its default value. 4. 5. Open the template or an instance configuration. Select the property you want to configure. Choose (Apply Changes). Procedure Setting a Template Custom Value for All Instances 1. in the Custom value field. 2. . Open the template configuration and select a service. 6. Restoring to Default Value 1. In Custom value. Select the property from the table displayed. Open the template or an instance configuration. manager or an application. Select a service. To create a new nested property. 5. Setting a Custom Value for a Specific Instance 1. A dialog box appears. manager or application. 3. Modifying Nested Properties 1. 4.

Choose the template configuration. Note You can configure more that one property for a service. enter the new template value. Proxy1 4. Choose the relevant application. 6. HeaderName=via represents two property strings: ReverseProxyMappings/ProxyConfigurations/Proxy1/ HttpProxyPort ReverseProxyMappings/ProxyConfigurations/Proxy1/Header/ HeaderName . o o In the field Value. where HttpProxyPort and HeaderName represent the property keys of the nested properties. Overwriting Instance Properties Values Use this procedure if you have set custom values on instance level and you want to overwrite them with template ones. Caution Only the property key is deleted. announcing that another value with higher priority is already set for the same property. Header 6. You have the following options: o Leave the property selected and choose OK. . select it and then choose Remove. Optional: You can enter a description for the property. ReverseProxyMappings 2. and then add the property name (key) at the end. EXAMPLE The following sample Java source: Syntax 1. 7. To delete a nested property. HttpProxyPort=80 5. 5. Choose (Apply Changes). 2. 3. enter a value for the property key. A dialog box appears. Select the property whose instance value you want to reset. manager or a service. 6.You have to first enter the path. using slashes. The property path cannot be deleted but it is no longer visible in the Config Tool. Choose (Apply Changes). manager or application before saving the changes. ProxyConfigurations 3. 4. 1. In the Custom Value field. Choose Set Custom Value.

o Deselect those template properties which you want to not overwrite the instances' ones. Part of the name is a valid string.The template value overwrites all the instances' values (if more instances) for the selected property. choose (Properties Search). 3. 2. More information: Java System Properties . Searching for Properties 1. To locate the property in Config Tool. On the Results pane. o Choose Cancel. Choose GO. 4. More Information You can also view and modify properties during runtime in the SAP NetWeaver Administrator. Choose Start. all the properties containing the string appear. To find a particular property. Each result line also displays the path and the values of the property. select the relevant result line. Enter the name of the property. None of the selected template properties will overwrite the instances' ones. Then choose OK.

browse to that position and select the node under which the new category/location will be inserted. o Categories are named according to the hierarchical structure known from file systems. The configuration steps are one and the same for both categories and locations. Typical problem areas are databases. The new element is added as a sub-node inside the Root Category or Root Location tree structure. and is used to emit trace messages. networking. and others. and is used to emit log messages. Procedure Adding a New Controller 1. 2. That is. Recommendation We recommend that you make your log configurations on instance level. the steps below are described for log controllers as a whole. Choose cluster <template_name> / <instance number> log configuration .describes messages that originate from source code areas. Editing and Removing Log Controllers Log controller is a Java object that manages the writing of log and trace messages. Two types of controllers are available:  Location . Select the categories or locations tab to create a new category or location.Adding. To add a new category/location in a particular position inside the tree structure. security auditing. 3.describes messages specific to distinguished problem areas. continue with the next step. This procedure helps you manage your log categories and trace locations. Choose New and then enter a name for the new log controller.  Category . The different hierarchical levels in a category name must be separated by "/". /System/Database (always starts with "/"). More information: SAP Logging API Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. . Then. respectively. Note These tasks have to be done with extreme caution and only by users experienced in the SAP Logging API. For example.

err. To add one or more destinations. Select the controller you want to delete and choose Remove 2. com.trc file to the locations System. Choose (Apply Changes). 2.Class.out and System. Therefore.o Locations are labeled according to the hierarchical structure known from Java packages. You can specify a destination where the log/trace messages to be written. Note You can remove only log controllers created by you. Removing a Controller 1.out to INFO.yourPackage. Select the controller you want to edit. choose the level of severity. Editing a Controller 1. 6. . respectively. 4. The new controller is added to the tree. Note Trace messages for standard output for STDOUT and STDERR are written in the defaultTrace. To remove a destination. Note If you have selected a particular node." character is used to demarcate the different layers in locations names. Choose OK. the Name field displays a path to the selected node. 5. and the severity level of System.err to ERROR. In Severity dropdown box. 3. choose Reset to Inherited Configuration. you only have to define the sub-name of your category/location at the end.sap. choose Add. choose Remove. More information: Appendix A: Severity Levels Note If you change the severity of the root node or of a particular sub-tree. the change takes effect to all subnodes under the root one. For example. Choose (Apply Changes). To return the original configuration from the AS Java installation. you have to set the severity level of System. The ". Select a destination and then chooseOK. To be able to see these trace messages. 4.

use Count field to specify the number of files. From Destinations tree. The log destination is also the object. specify the maximum number of bytes each log file can contain. It appears in the Destinations tree. to which you specify and assign a formatter. 2. 2. as well as optional filters. 6. In the second case. In case your destination is FileLog type. Procedure Adding a New Destination 1. or a rotating number of files.Adding. Choose Type dropdown list and select a destination type. Choose cluster <template_name>/ <instance_number> log configuration destinations . Choose any destination name from the tree and then choose New. use the Limit field to define in bytes the size of a file from the rotation stack. More information: Appendix A: Severity Levels. 5. A dialog box appears. Choose the Severity dropdown box to specify a severity level. 3. In Limit field. you can specify whether to be one file. Editing a Destination 1. Recommendation We recommend that you make your log configurations on instance level. Also. Enter a name for the new destination. specify the path to the file where messages will be written. . select the destination you want to edit. More information: Log (Destination) Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. The default ones are FileLog and ConsoleLog. Editing and Removing Log Destinations This procedure helps you manage the destinations where you want your log messages to be written. 3. 4. In Pattern field.

Note You can remove only destinations created by you. In Formatter field. select the destination you want to delete. More information: Formatter 8. Choose Remove.7. select a formatter. 2. Removing a Destination 1. . Choose (Apply Changes). 3. Choose (Apply Changes). That is the format in which the log destination will print the messages. From Destinations tree.

More information: Formatter Note You can configure and manage formatters for existing logs (destinations) only. The new formatter appears in the Formatters tree. select the formatter you want to edit. XMLFormatter. o TraceFormatter – formats log records in human readable format. From Formatters tree. A dialog box appears. Editing and Removing Log Formatters Each log type can print messages in different formats: TraceFormatter. Select any formatter from the tree and then choose New. This procedure helps you manage the log formatters. 3. Enter a name for the new log formatter and then choose OK. instance level.Adding. Procedure Adding a New Formatter 1. Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. and ListFormatter. The following are default ones: o ListFormatter – formats log records that can be transferred to and processed further by another application (for example. 2. Editing a Formatter 1. Note . Recommendation We recommend that you make your log configurations on 2. choose the formatter type. Choose cluster <template_name>/<instance_number> log configuration formatters . o XMLFormatter – formats log records as XML elements. You can specify a pattern to this format. From Type dropdown box. 3. by Log Viewer). Choose Pattern field to configure the formatter. If you do not specify such. the default one is created.

2. The pattern enables you to specify the message data fields. Choose (Apply Changes). select the formatter you want to delete and choose Remove. using a custom formatting pattern. Note You can remove only formatters created by you.For TraceFormatter you can make configuration. with placeholders of the form %[[-]<width>[]]<type>. 4. Choose (Apply Changes). From Formatters tree. . Removing a Formatter 1.

the set of five full files is converted into a ZIP file and stored as an archive on the file system. Prerequisites Start the Config Tool by double clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. To activate the log files archiving. 2. log archiving is disabled and the value is set to OFF. you must perform regular backups and keep all of your security log files. In Custom Value field. From the list of properties. 4. Therefore. Result Log archiving is activated. The default value for this property is empty.). 8. use the Log Viewer tool. To change the current log archive directory. enter the name of the new directory. 5. choose the ArchivesDirectory property. Procedure 1. each file with a maximum size of 10 MB. choose the ArchivedFileNames property. To see the archived logs. select ArchiveOldLogFiles. After the ZIP file is done. Choose cluster-data <template name> managers LogManager. When the fifth file is completed. Logs are written into five files. Choose Set Custom Value. 11. the new logs start overwriting the old log files. Choose (Apply Changes). In the Custom Value field. The default directory where archives of logs are stored is: <Drive>:\usr\sap\<SID>\JC<Instance number>\j2ee\cluster\<server>\log\archive. enter the names of the files to be archived.Configuring Log Files Archiving Use this procedure to configure automatic archiving of AS Java log files. If you enable the archiving process. If you want only certain log files to be archived. Choose Set Custom Value. Caution In several countries. 3. 9. 10. set the value as ON. in Custom value field. the backup of security logs is enforced by law. . 6. 7. By default. The log file names have to be separated by semicolon (. the new logs keep on overwriting the old log files. Choose Set Custom Value to apply the new value. This means that all log files will be archived.

This procedure enables you to export the whole cluster data as well as a particular cluster component data. . 4. 2. Procedure Exporting the System Configuration to an XML File 1. Choose File Restore From Backup . Choose OK. 3. You can also export AS Java data from the database and import it later.Exporting and Importing a Configuration You can save the changes you have made in the system configuration by exporting them as an XML file. Choose the directory. where you want to save the XML file. or just the instance ―.properties‖ file. Note When you import a configuration. 2. Thus you can restore the settings of the cluster components' properties. 3. Choose Open. Choose File Export Unsaved Changes to XML . Select the file you want to import. Prerequisites Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. to be fully compatible it has to be previously exported from the Config Tool. Enter a name for the XML file. Importing Data for a Particular Element 1.

Choose it to encrypt the secure store content.  Start the Config Tool by double-clicking the configtool script file in <SAP_install_dir>/<system_name>/<instance_name>/j2ee/configtool directory. If the secure store content is already encrypted. Procedure Encrypting the Secure Store Note To be allowed to enter a secure store key phrase. You cannot change the default key file location. in the dialog window. To manage the secure store. Make sure your JDK is provided with JCE Unlimited Strength Jurisdiction Policy Files by Sun Microsystems and they are installed on each used JRE. select the checkbox corresponding to AS Java is stopped. choose the Change Key Phrase button.Managing Secure Store Data This procedure enables you to administer the secure store data of the AS Java system. your AS Java needs to be stopped. 6. 4. Changing a Key Phrase Note To be allowed to change your secure store key phrase. 2. 5. choose cluster Secure Store . If your AS Java is stopped. Choose OK. your AS Java needs to be stopped. Choose (Apply Changes). 1. Prerequisites   Make sure your AS Java is provided with the IAIK package. You can also provide additional encryption of the secure store content. the files are migrated in a directory whose name corresponds to the relevant time stamp. Enter a key phrase for encrypting. the Encrypt Store button is enabled. 7. 1. a Logs window informs you about the success of the secure store migration and shows in which directory the secure store files are backed up. If the prerequisites are fulfilled. Note Every time you back up the secure store. . Dialog window Encrypting appears showing the encrypting progress bar. 3. When ready.

Choose (Apply Changes). If you want to add another property. Enter the relevant key and value. Choose (Apply Changes). Choose Connection Pools. 2. Select a property. Removing a Property 1. Choose OK. Editing the Secure Store Data 1. 3. Choose Remove. Select a property and edit its value. choose Add. Choose (Apply Changes). 5. You cannot change the key file location. 3. 3. enter the new key phrase. In the dialog window. 5. Make sure that the AS Java is stopped checkbox is selected. 4. 4. . 2.2.

More information: Log Viewer  Performing basic log viewing. searching. and customizing options available in the SAP NetWeaver Administrator. More information: Command Line Log Viewer .Log Viewing You can view all the logs and traces in AS Java using the following methods:  Viewing all logs and traces from the whole SAP NetWeaver system landscape by taking advantage of all the filtering. More information: Log Viewing with the SAP MC  Viewing all AS Java system log files in a command-line tool.

o If the information in the developer trace is insufficient or too detailed. SCS02). o The developer trace files of the Java instance are located in directory <Drive>:\usr\sap\<SAPSID>\<instance name>\work (Windows) /usr/sap/<SAPSID>/<instance name>/work (UNIX). o The developer trace files of the central services instance are located in directory <Drive>:\usr\sap\<SAPSID>\<instance name>\work (Windows) /usr/sap/<SAPSID>/<instance name>/work (UNIX) . You can check these files in case of errors or unexpected behavior during the startup process.Viewing Logs with the SAP Management Console The trace and log messages contain important information about system operation. J03). The data from the last three restarts is retained by default.  Dumping the Java Stack Trace . select the relevant process and choose ShowDeveloper Trace from the context menu.  AS Java logs The log and trace files generated by the AS Java processes and the applications running on top of AS Java are stored in directory <Drive>:\usr\sap\<SAPSID>\<instance name>\j2ee\cluster\server<n>\log (Windows)/usr/sap/<SAPSID>/<instance name>/j2ee/cluster/server<n>/log (UNIX). Using the SAP Management Console (SAP MC) log viewing functions you can:    View all system log and trace files View developer trace files Create stack traces for the processes Types of Log and Trace Files  Instance developer trace and log files contain information about the startup process. CE1) and<instance name> is the instance name of the Java instance (for example. choose Increment/Decrement Trace Level to adjust the launcher trace level to the required level. where <SAPSID> is the system ID (for example.CE1) and <instance name> is the instance name of the central services instance (for example. It is helpful to check and analyze them if you experience errors or unexpected behavior. Procedure  Viewing Developer Trace Files o To view the developer trace file of a process. where <SAPSID> is the SAP system ID (for example.

you can view all developer trace and log files of an instance by selecting the relevant instance. In the navigation pane. Note Alternatively. and choose Dump Stack from the context menu. select the relevant server process. The resulting Java server stack trace is stored in the dev_server<n> file in directory <Drive>:\usr\sap\<SAPSID>\<instance name>\work (Windows) /usr/sap/<SAPSID>/<instance name>/work (UNIX). 3. time. choose Show Developer Trace (see above). o To view the dump stack trace.  1. A dialog box appears. o To view the log file of the service. in which you can browse the log messages and view their detailed description. select the Log Files node from the tree structure of the relevant instance. and choosing List Developer Traces from the context menu. o To view log records filtered by severity. . select an instance and choose Show Trace File from the context menu. select an instance and choose Analyze Log Files. 2. and entries.o To dump the server processes Java stack trace. Log Viewing from the SAP MC To view all the log and trace files of an instance. select the file you want to view and choose Show Log File from the context menu.

Therefore.  Performance . whether for troubleshooting or for analysis purposes. Switching on or controlling the amount of log output is configurable at runtime without modifying the source code. Enabling logging is a major task. Tracing – classical trace messages. the API/method calls have to be simple and intuitive. it is common practice to insert logging statement within the code to produce informative logs at runtime. This framework has the following advantages:  Easy to use API . for distinguished problematic areas. . and then insert the output messages in the code. if you are interested in analyzing code problems.  Easy to maintain . Before executing the code in a productive system. While. In the SAP Logging API. Advantages The availability and readability of logs or traces are very important for both developers and administrators.switching on the logging mechanism must not degrade the performance of the application as if running with logging. What you have to do is classify the source area to be logged/traced. Therefore.enabling logs is not a popular task for a developer. Therefore. the destination. Implementation Considerations If you want to define distinguished problematic logistic areas.SAP Logging API During the development phase. developers are likely to use System. then trace messages are relevant. you should focus on log messages. the cleanup of these embedded lines can be very difficult. for coding problems.out.println in a sporadic manner or to call printStackTrace() in the case of an exception. this is not a flexible method to control the amount of log output. the messages are separated in two main areas:   Logging – classical log messages.the log insertion done by developer is totally decoupled from executing the code. and the message format. The terms used are described in the Key Components table after the figure. Note Without a standard logging framework. a common logging framework must be made available to satisfy the requirements of these groups. Integration The figure below represents a simplified version of the conceptual view that shows the key entities in the SAP Logging API.

Determines the format of the final message text. Log Formatter Filter Represents the destination where the message should be output.Conceptual View of SAP Logging Tool Key Components Term Log Manager Log Controller Log Record A structure that holds a message and its relevant data. Features The SAP Logging API provides the following functionality:    Using of both tracing and logging Making use of similarities between tracing and logging Cross-referencing between traces and logs . The Log Manager is part of the Java Enterprise Runtime and is the first manager to be started at system startup. Description A module that manages the process of logging system events. A Java object that manage the writing of log/trace messages. Optional means to further screen out messages.

   Language-independency for log messages Working with different output formats and destinations Controlled inheriting of code areas and message categories .

Specifies the type of the object to be created: log controller (C). The OID identifier must represent a unique name for the Log Configurator Service. LOG_ARCHIVE Syntax Description LOG_ARCHIVE Creates archive for all log files. Enables or disables additional console output for a specified log controller. or log formatter (F). LOG_DUMPS Syntax Arguments -? | -H OID Displays the help message. Turns the additional console output ON or OFF. The ID of the object to be created. The OID identifier must represent a valid name for the Log Configurator Service. Creates and registers new objects into the Log_Configurator Service. To change the settings of a newly created object you can use the LOG_EDIT command. They are added to the Shell environment by executing ―ADD LOG‖ on the command line.LOG Use This section contains the log commands used for AS Java log system administration. log destination (D). LOG_CREATE [-? | -H] OID] [-C | -D | -F OID Description Use the LOG_LIST command to obtain information about the existing objects. Note that if this log controller already has an . LOG_DUMPS [-? | -H] [OID] [ON | OFF] ON | OFF Description You can use the LOG_LIST command to obtain information about the existing controllers. LOG_CREATE Syntax Arguments -? | -H -C | -D | -F Displays the help message. The ID of the log controller to be debugged.

or log formatter (F). LOG_EDIT [-? | -H] [-C | -D | -F OID] OID Description You can use the LOG_LIST command to retrieve the current logging settings or the LOG_CREATE command to add a new object to the existing configuration. Specifies that a thorough info should be provided.associated log destination of type ConsoleLog some messages may be displayed twice. Keep in mind the hierarchy of the log controllers. The ID of the object to be edited. LOG_LIST [-? | -H] F [OID | -T]] [-T] [-C | -D | - -T The -T switch can be used as a single argument or after a type specifier (that is: -C. If neither ON nor OFF is specified. The OID identifier must represent a valid name for the Log Configurator Service. In this case the command behaves as if there is no T (the only difference is that a detailed information will be provided for the appropriate objects. If no OID is given – a "global" configuration is assumed. log destination (D). or -F). then the current status is shown. instead . Specifies the type of the object to be listed: log controller (C). LOG_LIST Syntax Arguments -? | -H -C | -D | -F Displays the help message. Note that only "named" objects can be edited (name is case sensitive). or log formatter (F). Reconfigures previously registered objects in the Log Configurator Service. LOG_EDIT Syntax Arguments -? | -H -C | -D | -F Displays the help message. log destination (D). and that this operation will affect all the users of the corresponding object. Specifies the type of the object to be edited: log controller (C). -D.

OID The ID of the object to be inspected. displays a thorough information about the settings of a particular object. the name of an object as printed by this command. and that this operation will affect all the users of the corresponding object. LOG_REMOVE [-? | -H] OID] [-C | -D | -F OID Description You can use the LOG_LIST command to retrieve the necessary information. The -T switch can be used only when no object ID is given. Shows information about the currently configured objects in the Log Configurator Service. it provides a complete listing of all registered object names sorted by their corresponding types. that is. The object identifier. The OID identifier must represent a valid name for the Log Configurator Service. then this command lists the name of every object of the respective type that is configured with the Log Configurator Service LOG_REMOVE Syntax Arguments -? | -H -C | -D | -F Displays the help message. If the command is used without arguments. If it is executed with a type specifier but with no object identifier. . The OID identifier must represent a valid name for the Log Configurator Service. The ID of the object to be removed. log destination (D). It must be used with a preceding type specifier but without the -T switch. Removes previously configured objects from the Log Configurator Service. Note that only "named" objects can be removed (name is case sensitive). Specifies the type of the object to be removed: log controller (C).of simple listing of their names). Description Only "named" objects can be displayed (name is case sensitive). or log formatter (F).