Debug logs and Logviewer concepts Part 1...

[former_member89217]

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 in a zipfile.  The UI and functionality is slightly different between Netweaver CE 7.11 and 7.3. This is part 1 of a 3 part series.  Part 2 will describe the same configurations in Netweaver 7.3 and part 3 will describe some additional general features and details.

Part 1  Netweaver CE 7.11

Initial Configuration

In  this test system  we have one Java server with two server processes(nodes). As such there are two Sourcing application instances and two sets of log and trace files generated.

Setting up debug logging

In the log configuration area of NWA, select Tracing Locations in the Show field.

Select DEBUG on the area or areas you want to set DEBUG logging on. Typically we select The E-Sourcing Folder, Set severity to Debug then use the Copy to Subtree button.  At this point you would see the selections shown below.  This currently includes SQL debug. Unless this is specifically asked for,  the suggested  setting would be to set the sql severity back to error.  Click save configuration.

Using Custom Views to limit files and filter content

In Netweaver CE, there are two separate sections in the UI to configure the files to be processed and how the content will be filtered.  

To begin the process, create a new view and select the directory locations that the files will be processed from. Typically for sourcing this will be all the locations that sourcing is deployed. In this case we have 2 server nodes, so we select these two locations.  Next add the content filters. The idea here is to limit the results to sourcing/clm entries for specific entries over a specific timeframe. This will provide a reasonably sized and concise output to be reviewed and or sent to support for analysis.  In this example we chose to filter by application, over a specific 6 day period and where the message contents contained the word script and free.  The severity filter is set to debug which does not limit any entries but used as an example this would typically be set to error to show only the error enties. The reference to “free”  in the message filter is make sure the the stats_monitor entries are included so we can monitor system usage while reviewing all other entries. This filtering can be as simple or complex as required .

Adding additional fields to the results to identify log entry source.

Using the customization option, the user can determine which columns are displayed in the filtered results.  A common reason to do this is to add detail needed to put the log entry into proper perspective. For this example we added system, instance and node columns…

In this example we added the system name, the instance and node so we could identify the sourcing instance responsible for each entry this would also allow you to sort by a specific instance. Keep in mind, these "columns" aren't actually data that is in the native Sourcing log.  This is information "generated on the fly" by Netweaver.

Downloading filtered results

Using the download content button on the logviewer section will allow the downloading of the content displayed. (minus  generated  columns).

Any content that exceeds 5Mb will be placed into 5Mb “chunks” and downloaded seperatly

The resulting pieces of the download log[1].csv – Log[n].csv