Introduction  |  Import a .war File into a New Project  |  Export a Project into a .war File  |  New MI Project

 

MDK Plug-in Configuration

To configure the MDK plug-in select following commands from the Eclipse menu: Window > Preferences > MDK

Dialog window for the MDK Plug-in configuration:

The dialog window of the configuration has three parts:

If you have only one MI runtime on your local computer (AWT or Tomcat) you just fill out the "MI home folder" of the runtime you have installed.

The options in detail:

Tomcat Runtime
  1. MI home folder
    Location of the Mobile Infrastructure client installation for Tomcat runtime on your local computer. This is the folder you selected during the installation process of the Mobile Infrastructure. By clicking onto the "..." button you can select the location interactively with the file explorer. It has to be a folder with the MI Tomcat runtime otherwise a warning message is displayed.
  2. Java SDK tools.jar file
    Location of the tools.jar file. The tools.jar file is part of the JDK and is necessary to compile the JSP. If the Mobile Infrastructure client installation has been properly finished, the tools.jar file is automatically located and the input field that contains the tools.jar file is disabled.
    If the tools.jar file cannot be found at the JDK location specified by the MI client installation (for example, when a Java Runtime path has been specified and not a Java Development Kit folder), the input field that contains the tools.jar file is enabled and you have to specify the tools.jar file manually.

    If the input field that contains the tools.jar file is enabled, you should check the MI installation, if a correct Java Development Kit folder has been specified to avoid MI startup problems or problems associated with JSP. When the MI installation finishes successful, it generates a 'startup.bat' file in the <ME_HOME> folder, that contains a 'SET JAVA_HOME=' command, that defines the JDK home folder. The JDK home folder is used to get the 'tools.jar' file.

  3. MI server name: Name/address of the local server on which the Mobile Engine is installed. The Mobile Infrastructure is based on a local Tomcat installation therefor the typical value will be 'localhost' or '127.0.0.1'. If none of the two values work use the full IP address and check the Tomcat installation of the Mobile Infrastructure.
  4. MI webapp root: URL to start the Mobile Infrastructure. The URL is added to the "MI server name" and the "MI webapp TCP port". Usually the URL is "mi" . The complete address according to the settings in the above shown dialog window would then be: http://localhost:4444/mi
  5. MI webapp TCP Port: TCP port used to connect to your (local) Tomcat installation. The standard value for the Mobile Infrastructure Tomcat installation is "4444".
  6. Command line to launch browser: Command line to start your browser.

If a correct MI home folder has been specified and the Command line for the browser has been filled out, the "Test Settings" buttons is enabled. When you click in the "Test Settings" button the options are tested. Tomcat is shut down and started up again. After the delay the browser is started with the URL to the Mobile Infrastructure. When the initial screen of the Mobile Infrastructure does not come up, please check your settings and refer to the chapter "Installation of the MDK". It also checks the existence of the tools.jar file.

AWT Runtime
  1. MI home folder
    Location of the Mobile Infrastructure client installation for AWT runtime on your local computer. This is the folder you selected during the installation process of the Mobile Infrastructure. By clicking onto the "..." button you can select the location interactively with the file explorer. It has to be a folder with the MI AWT runtime otherwise a warning message is displayed.
MI Logon Information
  1. MI logon user name: User name to log in to the Mobile Infrastructure. If you supply a user name and password, the Eclipse MDK Plug-in starts your application, registers you at the Mobile Infrastructure and starts your application directly. This can be a big time saver. If you leave this field blank, the Eclipse MDK Plug-in starts the MI Homepage and you have to log in manually (every time you start your application).
  2. MI logon password: Password to log in to the Mobile Infrastructure.

    The password is stored on disk and could be recovered. We recommend to use a password that is only used for development purposes.

 

Choose the OK button to store the settings and exit the configuration wizard.