NW Portal Logging and Tracing

The portal is logged using the standard central logging system of the AS Java. The Log Viewer tool in SAP NetWeaver Administrator allows you to view all logs and traces that are generated from the portal.
To ensure stable and error-free operation of the portal, you should check the logs regularly for error messages. If required, you can also configure the default logging settings to best meet your requirements.
Log and trace files contain information about the system execution:
Log files are mainly used by administrators to monitor the system operation and to perform error analysis. Therefore, logs are always switched on and get written automatically. They have predefined granularity (severity) that can be modified at runtime. Logs are typically written to categories specific to problem areas.
Trace files are mainly used by developers or support (engineers) to record and analyze the occurrence of certain events at runtime. Therefore, tracing is normally turned off. Traces can be switched on if a problem has occurred and a detailed analysis of a distinct aspect of the portal is necessary. Traces are typically written to locations that originate from specific source code areas.

You can access the trace files in the following ways

1.Log in to the portal using the following url http://<hostname>:<portno>/nwa

Navigate to  NWA -> Monitoring-> Logs and Traces -> from the dropdown select default trace.

2. If we have the O.S level credentials then all trace information is written to file defaultTrace.trc in directory \usr\sap\<SID>\JC<InstNo>\j2ee\cluster\server<n>\log on the J2EE Server.

How to check the default trace

  • Log on to the SAP NetWeaver Administrator as a system administrator (http://host:port/nwa). 
  • Go to the 'Log Viewer' (SAP NetWeaver Administrator » Problem Management » Logs & Traces » Log Viewer).
  • Open the 'Default Trace'.
  • Filter for the timeframe when the issue had happened.
  • Look / Search for entries related to 'com.sap.glx' or 'com.sap.bpem'.
  • In case the reported entry did not provide enough information to solve the problem and / or the trace entry looks like a defect in the application consider opening a message (How to increase the trace level)
Hint: If nothing was found try increasing the log level and try to redo the action (How to increase the trace level). Finally check again.

How to increase the trace level

  • Go to the 'Log Configuration' (SAP NetWeaver Administrator » Problem Management » Logs & Traces » Log Configuration).
  • Switch to 'Trace Locations'.
  • Select the node 'com.sap.glx' and/or 'com.sap.bpem'.
  • Set the trace level to 'Debug' or 'Info'.
  • Select 'Apply to sub-nodes'.
Hint: Make sure to set it back to its previous state (e.g. 'Error') once all needed data was collected. Otherwise it will generate a lot of data into the trace file.

No comments:

Post a Comment