|Oracle® Java Micro Edition Software Development Kit Developer's Guide
Release 3.3 for NetBeans on Windows
The Oracle 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.
The Multiple User Environment supports access from several accounts. It does not support multiple users accessing the SDK simultaneously. See "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 Oracle Java ME SDK 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.
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 "The Device Manager on Windows." A different user can then launch the SDK and own all processes.
The SDK directory structure conforms to the Unified Emulator Interface Specification (
http://www.oracle.com/technetwork/java/javame/documentation/ueispecs-187994.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:
bin. The bin directory contains the following command line tools. The default location of the bin directory is:
cref. The Java Card Platform Simulator tool, which is used to simulate smart cards in the emulator. It is used for testing SATSA (JSR 177) applications with the Oracle Java ME SDK. For more information on SATAS, see Chapter 20.
device-address is a tool for viewing, adding, and removing devices that the SDK is not able to discover automatically. See "Manage Device Addresses (device-address)"
device-manager. The device manager is a component that must be running when you work with Oracle Java ME SDK. After installation it starts as a service, and it automatically restarts every time your computer restarts. See "Emulators."
emulator. UEI compliant emulator. See "Emulator Command Line Options."
jadtool. Tool for signing MIDlets. See "Sign MIDlet Suites (jadtool)."
mekeytool. Management of ME keystores. See "Manage Certificates (MEKeyTool)".
preverify. The Java ME preverifier.
device-editor. Tool for creating new custom devices. See "Creating a Custom Device."
update-center. The Java ME SDK Update Center.
wma-tool. A command line tool for sending and receiving SMS, CBS, and MMS messages. See "Running WMA Tool."
wscompile. Compiles of stubs and skeletons for JSR 172. See "Generate Stubs (wscompile)".
docs. Release documentation.
legal. License and copyright files.
lib. JSR JAR files for compilation.
runtimes. CDC, CLDC, and IMP-NG 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:
To see the NetBeans user directory, click the Help menu and select About in the main window. The default location is:
Device working directories
The named subdirectories each correspond to an emulation device, as described in Table 8-1. Any detected external devices are also added to this directory space. Device detection is described in "Adding an External Device."
This directory contains the bean files for the adapter categories. The beans in this directory and subdirectories determine whether a skin is visible in the Device Selector, among other things. You should not manipulate these files directly.
See "Using the Custom Device Editor" for instructions on creating your own custom skin.
Both default skins and custom skins created with the Custom Device Editor are represented in the device-adapter directory.
Do not manipulate custom skin files from the operating system. All custom skin activity should take place in the Custom Device Editor.