different behavour of MAM application when starting via NWDS versus SAP MI

[Former Member]

Hello,

We have MAM25 installed and running and have implemented some modification. When I run and test the application from the NWDS everything works fine. But when I restart my laptop and I'm NOT using NWDS and start the mobile client and test the (already deployed) application from there, then the application is behaving differently some functionality that is created is working different.

It looks like that the mobile client is started with different startup parameters. Does anyone has the same experience? Is the Mobile client started differently from NWDS (via run application)? If yes, why?

Hope some one can help me?

Regards,

Ryan

[Former Member · Accepted solution]

Hello,

Most problems of this nature are coming from the classpath. Make sure it is the same for both environment.

Look at your startup.bat for how the classpath is made for the initial startup. The application classpath is loaded afterward (so in NWDS it should load AFTER the MI classpath as implementation can override one another).

Startup arguments are also in startup.bat. I usually do not use the Startup class in NWDS but the FrameworkInitializer class.

Thank you,

Julien.

msc mobile Canada inc.

http://www.msc-mobile.com

[Former Member · Accepted solution]

Hello Julien,

Thanks for your answer. But I'm not sure how to check the classpath and the startup class. may you can help me:

In nwds I see that when I run the application the main class is: com.sap.ip.me.mdk.api.runtime.Start and the arguments are: "-home:C:\Program Files\SAP Mobile Infrastructure" -trace -url:MAM25_V30/start -app:jsp. The class path from MAM is set to:

<classpathentry kind="src" path="java"/>

<classpathentry kind="var" path="JRE_LIB" rootpath="JRE_SRCROOT" sourcepath="JRE_SRC"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/db2ejdbc.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/crimson.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/jasper.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/jaxp.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/MEg.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/pinstall.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/servlet.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/webserver.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/system/crimson.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/system/jaxp.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP Mobile Infrastructure/lib/system/xalan.jar"/>

<classpathentry kind="lib" path="C:/Program Files/SAP/IDE/IDE70/eclipse/plugins/com.sap.ip.me.mdk.developmentTools_2.5.12/MDKExt.jar"/>

<classpathentry kind="lib" path="C:/j2sdk1.4.2_13/lib/tools.jar"/>

<classpathentry kind="lib" path="C:/SAPmi/MAM25_V30RDS/app-root/WEB-INF/lib/datetimepicker.jar"/>

<classpathentry kind="lib" path="C:/SAPmi/MAM25_V30RDS/app-root/WEB-INF/lib/MAM25_V21.jar"/>

<classpathentry kind="lib" path="C:/SAPmi/MAM25_V30RDS/app-root/WEB-INF/lib/mbscore.jar"/>

<classpathentry kind="lib" path="C:/SAPmi/MAM25_V30RDS/app-root/WEB-INF/lib/mbsrfid.jar"/>

<classpathentry kind="output" path="app-root/WEB-INF/classes"/>

When I run the application the following information message appears in nwds:

• MOBILE INFRASTRUCTURE 7.0 SUCCESSFULLY LAUNCHED **********

ME started with 'FrameworkInitializer' class and user 'rdou01'

When I start the mobile client using startup.bat. I see that the classpath variables are defined in the file listofjars.txt and set during startup. In these file I added the same path as mentioned before in nwds. Also in the same order. When I start startup.bat and I check the results in the doc command box. I see that the same librarie are loaded.

Still the application behaves different. Is there something else that I can check?

Regards,

Ryan

[Former Member · Accepted solution]

Hello,

Try putting you application code (the src folder) at the end of the class path (in project settings, go in the java build path, select the order tab and use the buttons to send the classpath down).

Thank you,

Julien.

msc mobile Canada

http://www.msc-mobile.com

[Former Member]

Thanks Julien,

You helped me out!!!

Regards,

Ryan