cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging MI 7.1 JSP App on NWDS 7.1 SP7

Former Member
0 Kudos

Hi Experts,

Can anybody explain me how to debug a JSP Application created on MI 7.1, NWDS version being 7.1 Support Pack 7? It will be great if anybody can point me the link to any resource available related to debugging JSP App on MI 7.1.

Thanks and Regards,

Gopal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Gopal,

NOTE: I assume you have maintained following settings.

1. Go to Window > Preferences > Select MDK

2. Maintain SAP NWM Client Home Folder , Client Logon User , Password.

3. Apply and Ok.

Now you can do following.

1. Open Mobile Infrastructure Perspective.

2. Select your JSP application Project.

3. Click on Export Project into a MI archive (.war/,jar) button

4. Select your projec

5. Check the Deployment folder path. it must point to the inbox folder located inside the SAP NWM Client Home Folder you mentioned in the settings above.

6. Check the check box Ass JSP as compiled classes

7. Check the check box for Run the Mobile Application

8. Click on Finish

This will launch your application on Mobile Client 7.1

But it will also create a Run and Debug configuraiton in NWDS.

Now stop the client using the terminate button on the console or use shutdown.bat and stopmonitor.bat files from the SAP NWM Client Home Folder.

Now do the following.

1. Put the break points in your application.

2. Follow Menu path Run > Open Debug Dialog...

3. Under MI Application your Project will be available.

4. Select your project

5. click on debug

This will launch your application in debug mode on Mobile Client 7.1

Hope this answers your question.

Thanks & Regards,

Abhijit

Former Member
0 Kudos

Hi Abhijit,

Thanks for providing the detailed steps. But I have already done what all you have told. Problem is following error props up while debugging:

Exception in thread "main" java.lang.NullPointerException

at com.sap.tc.mobile.cfs.startup.Startup.findLibraryURLs(Unknown Source)

at com.sap.tc.mobile.cfs.startup.Startup.main(Unknown Source)

Any idea on this error?

Thanks and Regards,

Gopal

Former Member
0 Kudos

Hi Gopal,

Can you add following to the debug launch configuration?

1. Follow Menu Path Run > Open Debug Path... > MI Application

2. Select your Projects Debug Configuration

3. Go to Arguments tab

4. In VM arguments text box add following

-Dmobile.home="<Absolute Path of SAP NWM Client Home folder>"

5. Click on debug

Thanks & Regards,

Abhijit

Former Member
0 Kudos

Hi Abhijit,

Thanks for response. I am still getting same error.

Best Regards,

Gopal

Former Member
0 Kudos

Hi Gopal,

There should be a modules folder inside the lib folder of the SAP NWM Client.

Is it there?

Can you check that?

Also on the NWDS console it will print the Mobile Client Home folder location.

Is it correct?

Thanks & Regards,

Abhijit

Edited by: Abhijit Suresh Shingate on Jun 8, 2009 12:28 PM

Former Member
0 Kudos

Hi Abhijit,

There is no modules folder inside lib folder.. I have given correct Home Folder path.

Best Regards,

Gopal

Former Member
0 Kudos

Hi Gopal,

That's the reason you are getting this exception.

Because lib\modules folder contains the Mobile Client framewrok jars which are mandatory.

And mobile client will try to load the classes from those jars as and when required.

During the startup it will put those jars in the class path.

If you run the client directly using the shortcut also then you will face the same issue.

Somehow the installation has got corrupted.

You need to re-install the client and then register it and then work with it.

There is no other way.

Thanks & Regards,

Abhijit

Former Member
0 Kudos

Hi Abhijit,

That's weird.... Ok I will do that and update thread by today evening.... Thanks for a lot for help.

Best Regards,

Gopal

Former Member
0 Kudos

Hi All,

It is weird that "MI Application Debug" was not working. But now debug issue is solved. Now I am using "Remote Java Application" Debug. In that I gave host as "localhost" and port as "45102".

Thanks and Regards,

Gopal

Answers (1)

Answers (1)

Former Member
0 Kudos

Problem in MI Application Debug. Resort to "Remote Java Application" Debug.