Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
CLDC Emulation on a Windows Mobile Device
Installing CLDC Emulation on a Windows Mobile Emulator
Managing Device Addresses (device-address)
Running the Emulator From the Command Line
Building a Project from the Command Line
Packaging a MIDLet Suite (JAR and JAD)
Command Line Security Features
Changing the Emulator's Default Protection Domain
Signing MIDlet Suites (jadtool.exe)
Managing Certificates (MEKeyTool)
Running the Payment Console From the Command Line
Virtual Machine Memory Profiler (Java Heap Memory Observe Tool)
Running the Java Heap Memory Observe Tool
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
JSRs 184, 226, and 239: Graphics Capabilities
JSR 205: Wireless Messaging API (WMA) Support
JSR 211: Content Handler API (CHAPI)
JSR 238: Mobile Internationalization API (MIA)
Options for running MIDlets in the emulator are as follows:
-Xautotest:JAD-file-URL
Run in autotest mode. This option installs a MIDlet suite from a URL, runs it, removes it, and repeats the process. The purpose is to run test compatibility kits (TCKs) with the emulator, using a test harness such as JT Harness, JavaTest™ or Java Device Test Suite (JDTS). For example:
emulator -Xautotest:http://localhost:8080/test/getNextApp.jad
Given the above command, -Xautotest causes the emulator to repeatedly install, run, and remove the first MIDlet from the MIDlet suite provided through the HTTP URL. Once the emulator starts, it queries the test harness, which then downloads and installs the TCK MIDletAgent.
-Xdescriptor:jad-file
Run an application locally using the given JAD file.
-Xdomain:domain-name
Set the MIDlet suite’s security domain.
-Xjam:command=application
Run an application remotely using the Application Management Software (AMS) to run using OTA provisioning. If no application is specified with the argument, the graphical AMS is run. The commands are as follows:
install=jad-file-url | force | list | storageNames|
Install the application with the specified JAD file onto a device.
force. If an existing application has the same storage name as the application to be installed, force removes the existing application before installing the new application.
list. List all the applications installed on the device and exit. The list is written to standard output before the emulator exits.
storageNames. List all applications installed on the device. The list is written to standard output before the emulator exits. Each line contains one storage name in numerical order. The list contains only the name so the order is important. For example the first storage name must be storage number 1.
Also:
run=[storage-name | storage-number]
Run a previously installed application. The application is specified by its valid storage name or storage number.
remove=[storage-name | storage-number | all]
Remove a previously installed application. The application is identified by its valid storage name or storage number. If all is supplied, all previously installed applications are removed.
transient=jad-file-url
Install, run, and remove the application with the specified JAD file. Specifying transient causes the application to be installed and run and then removed three times.
This example includes OTA installation:
emulator.exe -Xjam:install=http://www.myserver.com/apps/MyApp.jad -Xdevice:DefaultCldcMsaPhone2The above command returns the ID of the installed application. Once you obtain the ID you can run it with: emulator.exe=Xjam:run=ID
See also Running the Emulator From the Command Line, CDC Options, and Debugging and Tracing Options.