Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
Sign a CLDC Project With a Key Pair
Managing Keystores and Key Pairs
Working With Keystores and Key Pairs
CLDC Emulation on a Windows Mobile Device
Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
JSR 205: Wireless Messaging API (WMA) Support
JSR 211: Content Handler API (CHAPI)
JSR 226: Scalable 2D Vector Graphics
JSR 238: Mobile Internationalization API (MIA)
JSR 256: Mobile Sensor API Support
In the SDK, when you use Run via OTA your packaged MIDlet suite is installed directly into the emulator where it is placed in a security domain. The emulator uses public key cryptography to determine the appropriate security domain.
If the MIDlet suite is not signed, it is placed in the default security domain.
If the MIDlet is signed, it is placed in the protection domain that is associated with the root certificate of the signing key’s certificate chain. See Signing a Project.
In the Device Selection window, right‐click on the device and select Properties.
Find the Security Domain setting and make a selection from the context menu.
The SDK knows the runtimes the device can support and supplies only possible domains. The default for both MSA and JTWI is Maximum. See the topic “Setting Device Properties“.
Right-click on a project and select Properties.
In the Category area, select Running (the green triangle).
Select Regular Execution and check the Security domain box.
In this context regular execution means you are running in the emulator, as opposed to running OTA.
Select the domain from the drop-down menu.