Oracle® Java Micro Edition Software Development Kit Developer's Guide Release 3.0.5 for Windows E24265-04 |
|
Previous |
Next |
The Java ME SDK can be installed on a system running a supported operating system version. All users with an account on the host machine can access the SDK. This feature is called the Multiple User Environment.
Note: The Multiple User Environment supports access from several accounts. It does not support multiple users accessing the SDK simultaneously. See Section 8.1, "Switching Users". |
To support multiple users the SDK creates an installation directory that is used as a source for copying. This document uses the variable work to represent the SDK working directory and installdir to represent the installation directory. Each user's personal files are maintained in a separate working directory named javame-sdk
that has a subdirectory for each version installed.
To locate logs, see Section 14.1, "Device Manager Logs", and Section 14.2, "Device Instance Logs".
Multiple users cannot run the SDK simultaneously, but, you can run the SDK from different user accounts on the SDK host machine. When you switch users, you must close the SDK and exit the Device Manager, as described in Section 6.1.1, "The Device Manager on Windows". A different user can then launch the SDK and own all processes.
The Java ME SDK installation directory structure conforms to the Universal Emulator Interface Specification (http://java.sun.com/j2me/docs/uei_specs.pdf
), version 1.0.2. This structure is recognized by all IDEs and other tools that work with the UEI. The installation directory has the following structure:
apps
. Contains examples for supported platforms:
CDC and AGUI: AGUIJava2DDemo and AGUISwingSet2.
CLDC and MIDP: all other applications.
bin
. The bin directory contains the following command line tools. The default location of the bin directory is:
installdir\bin
cref.
Java Card simulator for working with SATSA JSR 177. See Section 20.2, "Java Card Platform Simulator (cref)".
device-address
is a tool for viewing, adding, and removing devices that the SDK is not able to discover automatically. See Section 13.2, "Manage Device Addresses (device-address)".
device-manager
. The device manager is a component that must be running when you work with Java ME SDK. After installation it starts as a service, and it will automatically restart every time your computer restarts. See Section 6.1, "Emulating Devices".
emulator.
UEI compliant emulator. See Section 13.3, "Emulator Command Line Options".
jadtool
. Tool for signing MIDlets. See Section 13.6.2, "Sign MIDlet Suites (jadtool)".
mekeytool
. Management of ME keystores. See Section 13.6.3, "Manage Certificates (MEKeyTool)".
payment-console
. Minimalistic console for viewing payment transactions. An equivalent tool exists in the Java ME SDK user interface.
preverify
. The Java ME preverifier.
resourcesmanager.
A tool for managing JSR 238 resource bundles. An equivalent tool exists in the Java ME SDK user interface.
wma-too
l. A command line tool for sending and receiving SMS, CBS, and MMS messages. See Section 22.3, "Running WMA Tool".
wscompile
. Compiles of stubs and skeletons for JSR 172. See Section 13.7, "Generate Stubs (wscompile)".
docs
. Release documentation.
ide-support
. The NetBeans integration file for Java ME SDK Plugin.
legal
. License and copyright files.
lib.
JSR JAR files for compilation.
pkg-toolkit. Packaging utility files.
runtimes
. CDC and CLDC runtime files.
toolkit-lib
. Java ME SDK files for configuration and definition of devices and UI elements. Executables and configuration files for the device manager and other SDK services and utilities.
These are the default NetBeans user directories.
NetBeans default project location:
C:\Documents and Settings\
user\My Documents\NetBeansProjects
To see the NetBeans Userdir, select Help > About in the main window. The location is:
C:\Documents and Settings\
user\.netbeans\
version
This documentation sometimes uses userhome to represent the root location of user files.
The javame-sdk
directory contains device instances and session information. If you delete this directory, it will be recreated automatically when the device manager is restarted.
C:\Documents and Settings\
user\javame-sdk
\version
Device working directories
C:\Documents and Settings\
user\javame-sdk\
version\work
The numbered subdirectories each correspond to an emulator, as described in Table 8-1.
Table 8-1 Device Names
Emulator # | Device | Platform |
---|---|---|
0 |
ClamshellCldcPhone1 |
CLDC |
1 |
DefaultCdcPbpPhone1 |
CDC |
2 |
DefaultCldcJtwiPhone1 |
CLDC |
3 |
DefaultCldcJtwiPhone2 |
CLDC |
4 |
DefaultCldcMsaPhone1 |
CLDC |
5 |
DefaultCldcMsaPhone2 |
CLDC |
6 |
DefaultCldcPhone1 |
CLDC |
7 |
DefaultCldcPhone2 |
CLDC |
8 |
DefaultCldcPhone3 |
CLDC |
9 |
VgaAGUIPhone1 |
CDC |
10 |
VgaCdcPhone1 |
CDC |
Device instances (device definitions). You can make a copy of a device instance, as described in Section 6.9, "Adding a Device Instance". Go to:
installdir\toolkit-lib\process\device-manager\device-adapter