Contact us

Frequently Asked Questions (FAQ)

Installation

Question:

Answer:


Question:

How can I install an MI for AWT and an MI for JSP on the same device?

Answer:

Installation of MI for AWT and MI for JSP can only be done on PCs, not on PDA. MI for AWT and MI for JSP are two different installations and on a PDA, the start link on the system's auto start folder can only start one of them.
On PCs, the problem is that MI is registered in the Windows Registry - and there is only on Registry entry, but you'd need two here. You therefore need to create an unregistered installation. This can be done simply by following these steps:

  1. Make sure that no MI is currently installed. If so uninstall the MI using the "Windows" commands Start -> Programs -> SAP Mobile Infrastructure -> uninstall.
  2. Install MI for AWT via its setup.exe file. To set the installation location, choose custom installation.
  3. Copy the entire folder structure of the MI installation
  4. Uninstall MI as described in 1.)
  5. Copy the MI installation back to its original location
    As the copying preserved all installation information (like JAVA_HOME, location of MI jars etc.), the MI for AWT is now fully functional and can be started via the startup.bat script in the installation directory of MI. The link on the desktop will not be there any more and there will be no system tray icon either. The installation is not registered with the operating system, but this causes no harm.
  6. Install MI for JSP via its setup.exe. To set the installation location, choose custom installation.
    This will install MI and register MI with the operating system. This installation has a desktop icon and a system tray icon to start and stop MI.

Question:

How can I start SAP NetWeaver Developer Studio or Eclipse with a specific Java VM version?

Answer:

In the shortcut you use to start the IDE, you can add the command line option -vm to specify the Java VM.

Example: The Java version you want to use is in folder C:\JDK1.3.1_09\jre\bin and your IDE is in folder C:\Eclipse.

Modify you shortcut so that it looks like that:

      C:\Eclipse\eclipse.exe -vm C:\JDK1.3.1_09\jre\bin\javaw.exe 

 


Question:

How do I check the version of the MDK?

Answer:

The MDK is always shipped together with the SAP NetWeaver Developer Studio and its Support Packages. To check the version of the Developer Studio and its plug-ins, you go via Help -> About SAP NetWeaver Developer Studio -> Plug-in details.

Example: MDK version number: 2.1.4.1 indicates that the current MDK version is for Mobile Infrastructure 2.1, 4 =4th Edition and 1 = first revised version.


Developing

Question

Are there any restrictions in using MI API's?

Answer

Do not use the Persistence API in addition to the SmartSync API.

Please also check the latest SAP Note 717510 for restrictions.


Question

Where can I find documentation about the handling of Eclipse.

Answer

When you are in Eclipse, select the Eclipse command "Help > Help Contents". Select "Java Development User Guide" in the contents section. There you will find a fully featured "Getting Started" section and you will learn how to set up perspectives, use the debugger and so on in the "Concepts" section.


Question

I tried to import a MDK example .war file with the MDK Plug-in. The new project shows an error.

Answer

If the error is not caused by a source program it is more likely the class path. Check the project properties in Eclipse (select project, click right mouse key and select Properties from the context menu). Check the "Java Build Path". If the Mobile Infrastructure libraries or the tools.jar library is referenced improperly, check the "MI Home" and "Location of tools.jar" setting in the MDK Plug-in Configuration. Press the "Test Settings" button which will check if it can find the Mobile Infrastructure and the tools.jar file.

 


Question

I deployed a application again but it seems that the older version of the JSP is activated.

Answer

Tomcat precompiles JSP. If you deploy an application under the same name it can happen, that the old precompiled version of the JSP is used. In this case delete all files in the Tomcat /work folder and start Tomcat again. Please also consider the MI class loader pitfalls described here.