| Exit Print View | |
Java Platform Micro Edition Software Development Kit Version 3.0, Mac OS |
|
|
|
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
The Java ME Platform SDK command line tools described in Manage Certificates (MEKeyTool) manage the emulator’s list of root certificates.
Real devices have similar lists of root certificates, although you typically cannot modify them. When you deploy your application on a real device, you must use signing keys issued by a certificate authority whose root certificate is present on the device. This makes it possible for the device to verify your application.
Each emulator instance has its own _main.ks file located in its appdb directory.
The micro keystore, _main.mks resides in the following directory.
Windows
installdir\runtimes\cldc-hi\appdb\_main.mks
Mac OS
installdir/runtimes/cldc-hi/appdb/_main.mks
This directory also contains keystore.ks and serverkeystore.ks. You can use the -import option to import certificates from these keystores as described in Manage Certificates (MEKeyTool).
|
|