Sun Java™ Wireless

Toolkit for CLDC

Create, Optimize, and Tune MIDP Applications —
Quickly and Easily

< The Sun Java™ Wireless Toolkit for Connected Limited Device Configuration (CLDC) (formerly
the J2ME™ Wireless Toolkit) is a state-of-the-art, award-winning toolkit for developing
wireless applications using the Java programming language. The toolkit includes build
tools, a device emulator, and monitoring tools for developing applications targeted at Mobile
Information Device Profile (MIDP) mobile devices. Hundreds of thousands of developers worldwide
use the toolkit to create, optimize, and tune MIDP applications quickly and easily.

The Java Wireless Toolkit for CLDC functions as Emulator and build environment support
a standalone development environment, or it Visit jcp.org
can be used with an integrated development • JSR 248 — Mobile Service Architecture
environment (IDE), such as the NetBeans™ • JSR 185 — Java Technology for the Wireless
Mobility Pack for CLDC. In standalone mode, Industry
you can use KToolbar to set preferences, create • JSRs 30 and 139 — Connected Limited
Highlights deployable MIDlet descriptor and archive files, Device Configuration 1.0 and 1.1
compile, test applications, and more. (A • JSRs 37 and 118 — Mobile Information
• Build applications with the push
of a button command-line interface is also available.) Device Profile 1.0, and 2.0
When using the Java Wireless Toolkit with an
• Build MIDP applications with
many combinations of optional IDE, developers benefit from the IDE’s capabili- Optional Packages
APIs ties, such as source-level debugging and GUI- • JSR 75 — PDA Optional Packages
• Choose customization options, building tools, including drag-and-drop MIDlets • JSR 82 — Java APIs for Bluetooth
emulator skins, and enhanced (available with NetBeans tools). • JSR 135 — Mobile Media API
screen features • JSR 172 — Java Platform, Micro Edition
• Profile methods, monitor network The Java Wireless Toolkit emulator, based on Web Services
and memory usage, and tune Java ME CLDC and MIDP reference implemen- • JSR 177 — Security and Trust Services API
performance tations, is fully compliant with the Technology • JSR 179 — Location API for J2ME
• Integrate with popular Java IDEs Compatibility Kit (TCK) for the supported Java • JSR 180 — SIP API for J2ME
Specification Requests (JSRs). This ensures that • JSR 184 — Mobile 3D Graphics API
Awards
• Developer.com Wireless all Java APIs in the specifications are present • JSRs 120 and 205 — Wireless
Development Product of the Year and correct. The toolkit provides a selection Messaging API
for 2004, 2005, and 2006 of emulator skins for application testing, and • JSR 211 — Content Handler API
• Software Development Jolt adding your own emulator skin is easy. • JSR 226 — Scalable 2D Vector Graphics
Product Excellence Award for API for J2ME
2004 and 2005 Figure 1 shows the toolkit’s flexibility. You • JSR 229 — Payment API
• Java Pro Readers Choice for 2004 can combine a target platform (MSA, JTWI, • JSR 234 — Advanced Multimedia
• JavaWorld™ Editor’s Choice or custom) with a profile and a configuration. Supplements
for 2003 You can also create a project that’s backwards • JSR 238 — Mobile Internationalization API
compatible with MIDP 1.0 and CLDC 1.0. • JSR 239 — Java Binding for the OpenGL®
ES API
2 Sun Java™ Wireless Toolkit for CLDC sun.com/software

MSA MSA Subset JTWI JTWI Custom gives MIDlets a broad range of new uses, such
MIDP 2.1 2.1 2.0 2.0 2.1 as responding to newly received email messages
or scheduled appointments or performing
CLDC 1.1 1.1 1.0 1.1 1.1
3 3
regularly scheduled tasks.
75 u u u

82 3 3 u u u
Content handlers
135 3 3 3 3 u The Content Handler API provides a way to
172 3 7 7 7 *** launch MIDlets in response to incoming content.
177* u u u u u For example, a device might launch a video
179 3 u 7 u u player MIDlet to handle incoming video content.

3 u u u u
The Java Wireless Toolkit makes it easy to map
180
3 3
content types to MIDlets, and you can also use
184 7 u u
the emulator to test the behavior of your
205 3 3 u u **
content handlers.
211 3 u u u u

226 3 3 7 7 *** Over-the-air application management

229 3 u 7 u u Users typically download applications over a
234 3 u u u u wireless network, a process that is commonly

3 u 7 u u
referred to as over-the-air (OTA), user-initiated
238
7 u
provisioning. The Java Wireless Toolkit includes
239 u u u
a small server that simulates a production OTA
3 Required u Optional 7 Not Available environment. Using this feature, you can easily
* 177 has four options: APDU, Crypto, PKI, and JCRMI. Any combination can be used. test provisioning of your applications without
** The custom target allows you to exclude WMA or to select 12o or 205 support.
135 is included by default, but not required. setting up and configuring an OTA server or
*** Web Services and JSR 226 require JAXP XML Parser moving MIDlet suite files. This utility is critical
if you want your applications to test MIDP 2.0
Figure 1. API selection options
features, such as the push registry or signed
MIDlets.

MIDP support Mobile device applications execute in specific

Built-in support for optional APIs
The Java Wireless Toolkit includes tools that MIDP 2.0 runtime protection domains. The
In addition to the extensive optional API support
support these and other MIDP features: Preferences dialog provides a selection of
built into the emulator, the Java Wireless
• An enhanced security architecture, including predefined protection domains that are specific
Toolkit provides utilities or preferences for
permission-based security and secure HTTPS to the chosen platform (for testing purposes
configuring a variety of APIs:
networking only). The toolkit also provides tools for signing
• Java APIs for Bluetooth (JSR 82)
• Ability of MIDlets to receive incoming net- MIDlet suites, including a test root certificate
Bluetooth is an important standard for local
work connections using a push registry accepted by the emulator to verify signed
wireless networking. The specification stan-
• Over-the-air installation of applications MIDlet suites. You can easily create your own
dardizes a set of Java technology APIs to
test keys and certificates from the signing tool.
allow these Java technology-enabled devices
Security support
to integrate into a Bluetooth environment
MIDP 2.0 applications must have permission to Push registry support
and includes basic support for the OBEX
perform network access or other sensitive MIDP offers a push registry to launch appli-
protocol.
operations. The toolkit’s Permissions dialog cations in response to incoming network
makes it easy to select and add permission connections or timers. With the Java Wireless
attributes to a MIDlet suite. Toolkit’s implementation of the push registry,
both an inbound network connection or a
timer-based alarm can activate a MIDlet. This
3 Sun Java™ Wireless Toolkit for CLDC sun.com/software

• J2ME Web Services Specification (JSR 172)

The Java Wireless Toolkit includes a stub
generator to simplify the process of accessing
Web services from MIDP applications.

• Location API (JSR 179)

The Location API allows applications equipped
with a Global Positioning System (GPS) or
other hardware to determine where the
device is located. You can set the simulated
location of the emulator at runtime or run a
script that changes the location automati-
cally over time.

• Session Initiation Protocol (SIP) API for

J2ME (JSR 180)
The (SIP) provides a standard way for appli-
cations to communicate. It can be used to Figure 2. The network monitor tracks SIP messages and responses.
manage instant messaging, text chat, voice
chat, videoconferencing, and other types
of communication. The toolkit simplifies • Scalable 2D Vector Graphics API for J2ME • Mobile Internationalization API (JSR 238)
your development because it provides a (JSR 226) This API provides a way for applications to
basic SIP proxy server and registrar for you. The API for Scalable Vector Graphics (SVG) be displayed in multiple languages and used
SIP messages and responses can be viewed supports interactive 2D graphics written in in multiple countries. Resources are stored
in the network monitor. XML. Useful features include animation and in files in a format defined in JSR 238. The
the ability to create graphics that adapt to resource files are bundled as part of the
• Wireless Messaging API (WMA) (JSR 120 the display resolution and form factor of the MIDlet suite JAR file. The toolkit provides a
and JSR 205) current device. resource manager that simplifies the job of
Sending short text messages with mobile creating and maintaining resource files.
devices is increasingly popular. Using the • Payment API (JSR 229)
Wireless Messaging API (WMA), devices have JSR 229, the Payment API, enables applica- • Java Binding for the OpenGL® ES API
the ability to exchange Short Message Service tions to make payments on behalf of their (JSR 239)
(SMS) and other messages from MIDP and users. It supports different payment mecha- The OpenGL® for Embedded Systems
other Java platforms. The toolkit includes a nisms through payment adapters. The (OpenGL® ES) API is a low-level graphics
WMA console, a utility that enables message emulator implements the Payment API library suitable for accessing hardware-
exchange with the emulator. Messages can with a sample payment adapter that simu- accelerated 3D graphics. JSR 239 defines the
be sent between emulators or from the lates both Premium Priced SMS (PPSMS) Java programming language bindings for the
console itself to an emulator, and they can and credit card payments. KToolbar provides OpenGL® ES API.
even be broadcast to all running emulators. forms for setting up payment attributes and
preferences. A payment console enables you
to easily track payment attempts and record
success or failure.
4 Sun Java™ Wireless Toolkit for CLDC sun.com/software

Performance monitoring and tuning

The Java Wireless Toolkit enables you to monitor
and performance-tune your applications. The
tools available to developers include:
• Method profiler — highlights application
bottlenecks by showing the methods an
application called, how often they were
called, and the time spent in each method
• Memory monitor — shows the memory a
MIDlet uses as it runs and the current
memory in use for each object.
• Network monitor — shows a MIDlet’s network
connections, including the values of all HTTP
requests and responses between the client
and the server. It also monitors various other
communication protocols, as shown in
Figure 2.
Figure 3. WMA messaging in KToolbar, the WMA console, and the default emulator. The WMA
Customization console and the emulator send and receive messages. KToolbar displays project information.
You can easily create new emulator skins for the
toolkit’s default emulator, changing the screen About Sun You’ll receive a monthly newsletter packed
size, modifying display colors, repositioning A singular vision, The Network is the Computer™, with information on the latest innovations,
buttons, and more. drives Sun in delivering industry-leading tech- plus access to a wealth of resources. Register
nologies that focus on the whole system — today to join the Sun Inner Circle Program at
Java Wireless Device Custom Toolkit where computers, software, storage, and serv- sun.com/joinic.
For further customization, you can purchase a ices combine. With a proven history of sharing,
technology license for the source code from building communities, and innovation, Sun For more information on the Java Wireless
Sun. The license allows you to create custom helps create opportunities, both social and Device Custom Toolkit, see www.sun.com/
versions of the Java Wireless Toolkit. Or Sun can economic, around the world. You can learn software/jpe/es. To learn more about the Java
customize the source code for you to build an more about Sun at sun.com. Platform, Micro Edition, visit java.sun.com/
emulation environment for your specific devices javame. To download the Java Wireless Toolkit,
or networks. You can also use the package to Learn more visit java.sun.com/products/sjwtoolkit.
build a custom development environment Get the inside story on the trends and tech-
based on open standards. nologies shaping the future of computing by
signing up for the Sun Inner Circle Program.

Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 USA Phone 1-650-960-1300 or 1-800-555-9SUN Web sun.com
© 2007 Sun Microsystems, Inc. All rights reserved. Sun, Sun Microsystems, the Sun logo, Java, J2ME, JavaWorld, NetBeans, and The Network is the Computer are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States and other countries. OpenGL is a registered trademark of Silicon Graphics, Inc. Information subject to change without notice. SunWIN #: 502877 Lit. #: SWDS12646-0 4/07