Beginners Guide to J2ME Programming Architecture

J2ME is a highly optimized Java run time environment. J2ME is aimed at the consumer and embedded devices market. This includes devices such as cellular telephones, Personal Digital Assistants (PDAs) and other small devices .Below diagram explain the detail. Mobile devices come with different form, features and functionality, but often use similar processors and have similar amounts of memory. Therefore configurations were created, defining groups of products based on the available processor power and memory of each device. A configuration outlines the following:

                

       J2ME Specification and Configuration   

   

J2ME Configuration (Description)

Mobile devices come with different form, features and functionality, but often use similar processors and have similar amounts of memory. Therefore configurations were created, defining groups of products based on the available processor power and memory of each device. A configuration outlines the following:

J2ME Connected, Limited Device Configuration (CLDC)

•    Configuration for mobile phone, pager and wireless devices
•    160 – 512k of memory available for Java  application 

J2ME Connected Device Configuration (CDC)

•    Configuration for television, communicator.
•    Base system based on 32-bit processor
•    2MB or more of total memory available for Java application.

J2ME  Profile

A profile defines the type of device Supported.

J2ME Profiles BASED ON CLDC

Kjava

Kjava is Sun’s proprietary profile and contains the Kjava API.  The Kjava virtual machine, KVM, accepts the same byte codes and class file format as the classic J2SE virtual machine.
Kjava contains a Sun-specific API that runs on the Palm OS. The Kjava API has a great deal in common with the J2SE Abstract Windowing Toolkit (AWT). However, because it is not a standard J2ME package, its main package is com.sun.kjava.

J2ME Mobile Information Device Profile (MIDP)

MIDP is geared toward mobile devices such as cellular phones and pagers.MIDP is a common, industry-standard profile for mobile devices that is not dependent on a specific vendor. It is a complete and supported foundation for mobile application development.

J2ME Profiles BASED ON CDC

J2ME Foundation Profile, Personal Basis, Personal and RMI profiles are based on CDC .

JABWT (Java APIs for Bluetooth Wireless Technology)

Applications running on the Java platform access Bluetooth through the Java APIs for Bluetooth Wireless Technology (JABWT, also called BTAPI), an optional package that can be used with any J2ME configuration or profile. JABWT is defined as JSR 82 within the Java Community Process. The specification was finalized in 2002, but only recently have J2ME-enabled devices that support JSR 82 appeared. Of course, Bluetooth support at the device level is a prerequisite for JABWT support. As more Bluetooth-enabled devices make it to market, you can expect to see greater support for Java-based Bluetooth programming.

Submitted By

Sarathraj completed BE (Computer Science and Engg ) underAnna

University .

phone(r):0479-2431986 Mob:     9847096007
Other Works  Same Author
Bluetooth Enabled Person Identifiction System