Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
Specify the Security Domain for an Emulator
Specify the Security Domain for a Project
Sign a CLDC Project With a Key Pair
Managing Keystores and Key Pairs
Working With Keystores and Key Pairs
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 Keystores Manager opens.
If you prefer a different keystore, select Add Keystore to create a new keystore or add an existing keystore.
You must provide an alias to refer to this key pair.
The six Certificate Details fields are provisionally optional. You must complete at least one field.
Key Pair Alias. The name used to refer to this key pair.
Common Name. Common name of a person, such as "Jane Smith"
Organization Unit. Department or division name, such as "Development"
Organization Name. Large organization name, such as "Sun Microsystems Inc."
Locality Name. Locality (city) name, such as "Santa Clara"
State Name. State or province name, such as "California"
Country. Two-letter country code, such as "US"
The password is optional. If you do provide a password, it must have at least six characters.
The new key is displayed in the Keys area under its alias. You can now select this keypair when you sign a project. See Signing a Project.