Skip to main content

How to check logs for particular J2EE application issue



Purpose

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.

Example Scenario

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.


Solution

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):

/wp-content/uploads/2014/11/1_587211.png

Now click on “More Actions” ——> “View Logs” to get a list of all logs that were populated for this application: tc~wd~dispwda.
/wp-content/uploads/2014/11/2_587212.png

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.

/wp-content/uploads/2014/11/3_587222.png

It is also possible to differentiate between HTTP requests that were made for this application and the Session logs:



/wp-content/uploads/2014/11/4_587223.png

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.

/wp-content/uploads/2014/11/5_587224.png

Now add a filter and enter the application name (tc~wd~dispwda in this case).

/wp-content/uploads/2014/11/6_587225.png

Click on Apply and all logged entries for the application tc~wd~dispwda will be available now:

/wp-content/uploads/2014/11/7_587226.png

For a similar document on how to searching for specific error content in ABAP server logs, check:
http://scn.sap.com/docs/DOC-57078

source: scn.sap.com

Comments

  1. This comment has been removed by the author.

    ReplyDelete
  2. Nice article please do visit my website for j2ee java training

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP ST-PI and ST-A/PI Patch Update Steps

SAP ST-PI and ST-A/PI patch update Summary :- This document will show you how to update the ST-/PI and ST-A/PI in SAP with help of service preparation check RTCCTOOL . Author: Brindavan Mookaiah Designation : SAP BASIS Consultant Tabls of content 1) EWA report 2) Run RTCCTOOL 3) Implement the ST-A/PI and ST-PI Step 1) Check the EWA report about the ST-PI and ST-A/PI patch to update. SAP will recommend upgrading the new version based on SAP Application. Steps 2) Once if you able to see that the ST-A/PI & ST-PI  need to update and SAP recommeded. Then login into SAP and go to T-code SE38 and then execute program  ‘RTCCTOOL ‘. Download the latest ST-PI and ST-A/PI from service market place http://www.service.sap.com Once you downloaded  the required file(ST-PI& ST-A/PI) from market place and copy the file into the server. Mostly this file will be SAR file. Login in to OS level with SIDadm and extract the file using SAPCAR....

How to export RFC destinations prior Refresh

The best and easiest way... Goto SE01, create transport request (Transport of Copies) R3TR TABU RFCATTRIB * R3TR TABU RFCDES * R3TR TABU RFCDOC * R3TR TABU RFCSYSACL * If you take only RFCDES you will be missing the Documentation part of RFCs in order to take everything you need to have export of all the above mentioned tables.

Setup JCo RFC Destination for ABAP system

SAP JCo RFC Destination: SAP JCo connector is using for Java Application to communicate with SAP ABAP system via Remote Function Call (RFC). JCo RFC support bi-directional for communication like Java to ABAP system and ABAP system to Java system. To Access the JCo RFC, We need to login with Visual Administrator. Maintaining a JCo connection in the portal Visual Administrator : Goto the Path: Drive\usr\sap\<SID>\JC<nr>\j2ee\admin\go.bat Click on –> Connect Provide the Password and click on –> Connect Now you have successfully connected the Visual Administator. Next, Go to <SID> –> Server 0(node)–>Services –>JCo RFC Provider Provide the details like below: Click on –>Set We have completed the JCo RFC destination. Now, we need to login in ABAP system and test the RFC. Login to system. Go to Tx. SM59. Select the TCP/IP connections Click on –>Create...