Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0, Mac OS

Get PDF Book Print View

Document Information

Getting Started


Using Sample Projects

Creating and Editing Projects

Viewing and Editing Project Properties

Running Projects in the Emulator

Searching the WURFL Device Database

Finding Files in the Multiple User Environment

Profiling Applications

Network Monitoring

Lightweight UI Toolkit

Security and MIDlet Signing

Security Domains

Setting Security Domains

Signing a Project

Sign a CLDC Project With a Key Pair

Managing Keystores and Key Pairs

Working With Keystores and Key Pairs

Create a Keystore

Add an Existing Keystore

Create a New Key Pair

Remove a Key Pair

Import an Existing Key Pair

Managing Root Certificates

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)

On-device Debugging

Command Line Reference


JSR Support

JSR 75: PDA Optional Packages

JSR 82: Bluetooth and OBEX Support

JSR 135: Mobile Media API Support

JSR 172: Web Services Support

JSR 177: Smart Card Security (SATSA)

JSR 179: Location API Support

JSR 180: SIP Communications

JSR 184: Mobile 3D Graphics

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 226: Scalable 2D Vector Graphics

JSR 229: Payment API Support

JSR 238: Mobile Internationalization API (MIA)

JSR 256: Mobile Sensor API Support


Managing Root Certificates

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.



Mac OS


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).