Debug logs and Logviewer Concepts Part 3…

Introduction

The Netweaver Log viewer is a versatile tool that provides access to all Netweaver logs as well as logs from deployed applications such as SAP Sourcing / CLM.   The filtering capabilities of the tool provide access to a specific node or all nodes with the results merged into a single display.  In addition to the display capabilities, the tool also provides download capabilities for either the filtered content or the raw log files. When the content results exceed 5MB, the tool automatically generates separate 5MB .csv files.  In the case of the raw log files, the tool automatically compresses the files into a zipfile.  The UI and functionality is slightly different between CE 7.11 and 7.3. This is part 3 of the 3 part series.

Part 3  General Concepts

Getting results from other non-clustered systems.

Another convenience of the log viewer is the ability to connect to remote systems and get log content from them.  This is done using the Open External File option in the Log Files menu option.  Once selected, the user can supply the host and port (5XX13) to access the remote system

Checking  files and source for the content

Understanding where the content is coming from and how much content there is based on the current filtering is an interesting thing to know before downloading any content. The log viewer provides a couple ways to determine this…

Also mouse over a particular rule tells you how many files it results in…..

Other useful log viewing options

Under Show View –> General   (View –> Open View in 7.3) there are several  default  views that can show items like Text Formatted (Unstructured Log Files in 7.3).  This option allows access to Netweaver startup logs, deployment logs and items like the available.log file which shows a when the application server was up and available

.

Default View  for SAP Logs   Open View –> SAP Logs.

Specific log items to look for

Following system loading concurrent users and memory usage:

By adding the filter for stats_monitor only the lines that contain the number of users and the used/free memory will be displayed this will make it easy look at system loading/performance issues.  We would suggest using this in conjunction with adding the server instance and node info to the table so each individual instance can be monitored independently…

Debugging Scripts:

In the latest versions of 7.X , 9.X and in upcoming 10.X versions, there have been enhncements to the logging of script activity.  There are some specific strings that could be used to find all the script activity.

The following are some example log lines:

01:06.7  DEBUG local4 ScriptEnvironment execute RequestHandler.RqThread: fullsave 624931f7b3a87d3476a8bb50a3cd244a8d995a1b #biogenyx# ghrob   “executing script: System.err.println(“”*** HRG Field Validation ***””);”

01:06.8 scripting INFO local4 com.sap.odp.comp.scripting.ScriptManager “markLog(SessionContextIfc, String” RequestHandler.RqThread: fullsave 624931f7b3a87d3476a8bb50a3cd244a8d995a1b #biogenyx# ghrob   end: executeFieldScript for DISPLAY_NAME on PROCAT-006-BGNXM-2013 [ELAPSED TIME: 39 ms]

01:07.3 scripting INFO local4 com.sap.odp.comp.scripting.ScriptManager “markLog(SessionContextIfc, String” RequestHandler.RqThread: fullsave 624931f7b3a87d3476a8bb50a3cd244a8d995a1b #biogenyx# ghrob   begin: executeCollectionScript on PROCAT-006-BGNXM-2013 CollnId: COLLABORATORS

01:07.3  DEBUG local4 ScriptEnvironment execute RequestHandler.RqThread: fullsave 624931f7b3a87d3476a8bb50a3cd244a8d995a1b #biogenyx# ghrob   “executing script: System.err.println(“”*** HRG Collection Validation ***””);”

01:07.4 scripting INFO local4 com.sap.odp.comp.scripting.ScriptManager “markLog(SessionContextIfc, String” RequestHandler.RqThread: fullsave 624931f7b3a87d3476a8bb50a3cd244a8d995a1b #biogenyx# ghrob   end: executeCollectionScript on PROCAT-006-BGNXM-2013 CollnId: COLLABORATORS [ELAPSED TIME: 36 ms]

As you can see there are some new tags that could be used to find/filter this activity.

executing script:

ScriptEnvironment (DEBUG logging enabled)

scripting.ScriptManager

For functionality improvements make note that there are start and end tags on execution as well as a Elapsed Time indicator. This will be valuable in cases

where performance issues arise and it is not clear where excessive time is being spent. Also note that the begin:, end: and elapsed time: log entries do not require DEBUG logging enabled.

Known Issues:

Filtering does apply to content export but layout customization does not. Since this is the case, when using this tool to export results from multiple nodes, one would need to use the “All Columns” option so that location of the content is understood.