How to check logs for particular J2EE application issue
The purpose of this document is help in searching for specific content in the SAP Netweaver Application Server JAVA for more information on a particular J2EE application. This can be a very tedious affair if many server nodes are configured and this document explains how to do this from the SAP server end using /nwa (SAP Netweaver Administrator), rather than logging to the operating system to search the actual trace file.
Lets say that the J2EE Webdynpro application (tc~wd~dispwda) is constantly going down or end users are getting Webdynpro related issues and you as the Basis Administrator would like to investigate further. The issue is not occurring now and a root cause analysis is needed. You would ideally check all the default trace files for this issue (any error related to the application tc~wd~dispwda) so that any discrepancies can be monitored.
Now searching all trace files can be a cumbersome affair particularly if many J2EE server nodes configured and depending on the trace severity set, these files can be very large at times.
The SAP Netweaver Administrator utility (NWA) gives you an easy way of doing this check.
Navigate to: http://<server hostname>:port/nwa ——>Operations ——>Start&Stop ——>Java Applications——>and enter the application name (tc~wd~dispwda in this case):
You will be directed to the Log Viewer application and here you can find more detailed logs on the operations that were done on / by the application: tc~wd~dispwda.
It is also possible to differentiate between HTTP requests that were made for this application and the Session logs:
You can also access this information straight from the log viewer application. Navigate to http://<server hostname>:port/nwa ——>Troubleshooting ——>Log ViewerStart&Stop ——>Show advanced filter.
Now add a filter and enter the application name (tc~wd~dispwda in this case).
Click on Apply and all logged entries for the application tc~wd~dispwda will be available now:
For a similar document on how to searching for specific error content in ABAP server logs, check: