MIDP App Deployment Procedure

MIDP APPLICATION DEPLOYMENT PROCEDURE : 

Soner Aydemir MIDP APPLICATION DEPLOYMENT PROCEDURE

CONTENTS : 

Wireless Java Application Categories Wireless Java Applications Development Lifecycle Deploying and Running Remote Applications An Example of Deploying and Running an Application by using Nokia cell phone. CONTENTS

Wireless Java Applications : 

Wireless Java applications fall into two broad categories: Local applications (also called stand-alone applications) perform all their operations on a handheld wireless device and need no access to external data sources through a wireless network. Examples include calculators and single-player games. Network applications consist of some components running on a wireless device and others running on a network, and thus depend on access to external resources. An example would be an email application, with a client residing on a wireless phone that interacts with a Simple Mail Transfer Protocol (SMTP) server to send messages. Wireless Java Applications

Slide 4: 

Although these two types of applications are different, they are deployed in the same way. Local applications are easier to test than network applications. For example, a calculator application can run on a wireless phone even when it is not connected to any network, but an email client won't work without a connection to the SMTP server that actually transmits the messages.

Wireless Java Applications Development Lifecycle : 

The development life-cycle of MIDlets and other wireless Java applications comprises three steps: Write the application.  Test the application in an emulation environment.  Download the application to a physical device and test it. Once you are happy with the application's performance on one or more emulators, download it to a real device and test it there. If it's a network application, test it on a live wireless network to ensure that its performance is acceptable. *I will focus on last step. Wireless Java Applications Development Lifecycle

Deploying and Running Remote Applications : 

Deploying and running applications in an emulation environment is a very good way to test the logic and flow of your application generally, but you won't be certain it will satisfy users until you test it on a real physical device connected to a wireless network. Your application's performance may be stunning in the emulator, which has all the processing power and memory of your desktop machine at its command, but will it perform well on the handheld device, with its limited memory and processing power, low bandwidth, and other constraints? To perform realistic tests you need a J2ME-enabled physical device, and a data cable to connect it to your desktop Deploying and Running Remote Applications

Basic Things to Know : 

We won’t pass class files directly to a MIDP to deploy an application. Instead, we will package them in a Java Archive (JAR). Manifest Information: Every JAR includes a manifest file, META-INF\MANIFEST.MF, that describes the contents of the archive. For MIDlet JARs, the manifest file must contain extra information. The extra information is stuff that’s important to the MIDP runtime environment, like the MIDlet’s class name and the versions of CLDC and MIDP that the MIDlet expects. Basic Things to Know

A Manifest File: : 

MIDlet-1: Assignment1, Assignment1.png, Assignment1 MIDlet-Name: Assignment1 MIDlet-Vendor: Soner MIDlet-Version: 1.0 MicroEdition-Configuration: CLDC-1.0 MicroEdition-Profile: MIDP-2.0 A Manifest File:

APPLICATION DESCRIPTOR (.JAD) : 

One additional file is needed before our MIDlet is ready to deploy. An application descriptor file must be created. This file contains a lot of the same information that’s in the MIDlet JAR manifest file. However, it lives outside the JAR and enables application management software to learn about a MIDlet JAR without installing it. APPLICATION DESCRIPTOR (.JAD)

A .JAD FILE: : 

MIDlet-1: Assignment1, Assignment1.png, Assignment1 MIDlet-Jar-Size: 3207 MIDlet-Jar-URL: Assignment1.jar MIDlet-Name: Assignment1 MIDlet-Vendor: Soner MIDlet-Version: 1.0 MicroEdition-Configuration: CLDC-1.0 MicroEdition-Profile: MIDP-2.0 A .JAD FILE:

An Example by Using Nokia : 

Create a Wireless Toolkit Project An Example by Using Nokia

Slide 12: 

Put Your Source file (.java) to the directory that I show below:

Slide 13: 

Run it and Test it by using emulator:

Slide 14: 

Run it and Test it by using emulator:

Slide 15: 

The files in “bin” folder before we create a .jar file: There are only .jad and manifest files

Slide 16: 

Create a .jar file in WTK:

Slide 17: 

The files in “bin” folder after we create a .jar file: You can just copy the .jar file to your phone to finish the deployment procedure .

Slide 18: 

Thank you for your attention