Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 User Manual
Product codes
6203
Java User’s Guide
9.2 Compile
57
wm_java_usersguide_v19
Page 56 of 109
2012-01-27
Confidential / Released
9.2
Compile
•
Launch a Command Prompt. This can be done from the Programs menu or by typing "cmd"
at the Run... prompt in the Start menu.
at the Run... prompt in the Start menu.
•
Change to the directory where the code to be compiled is kept.
Compile the program with the SDK. Examples of build batch files can be found in each sam-
ple program found in the samples directory "Documents and Settings\All Users\Cinterion
ABC2 WTK Examples\WTKSamples" under Windows XP or "Users\Public\ Cinterion ABC2
WTK Examples\WTKSamples" under Windows Vista and above. The samples directory
can be opened directly via the WTK start menu entry.
Compile the program with the SDK. Examples of build batch files can be found in each sam-
ple program found in the samples directory "Documents and Settings\All Users\Cinterion
ABC2 WTK Examples\WTKSamples" under Windows XP or "Users\Public\ Cinterion ABC2
WTK Examples\WTKSamples" under Windows Vista and above. The samples directory
can be opened directly via the WTK start menu entry.
•
If the compile was successful the program can be transferred to the module and executed
as described in the following chapters.
as described in the following chapters.
The batch files for compiling the samples are using the system environment variables
JAVA_HOME_ABC2 and WTK_HOME_ABC2. The first one points to the root directory of the
installed JDK and the second one to the root directory of the Cinterion-CMTK-<productname>-
IMPNG installation. The installation process sets these environment variables. A modification
is usually not necessary.
JAVA_HOME_ABC2 and WTK_HOME_ABC2. The first one points to the root directory of the
installed JDK and the second one to the root directory of the Cinterion-CMTK-<productname>-
IMPNG installation. The installation process sets these environment variables. A modification
is usually not necessary.
9.3
Run on the Module with Manual Start
•
Compile the application at the prompt as discussed in
or in an IDE.
•
Transfer the .jar and .jad file from the development platform to the desired directory on the
module using the Module Exchange Suite or OTA provisioning.
module using the Module Exchange Suite or OTA provisioning.
explains how to
download your application to the module.
•
Start a terminal program and connect to ASC0.
•
The command AT^SJRA is used to start the application and is sent to the module via your
terminal program. Either the application can be started by .jar or by .jad file.
terminal program. Either the application can be started by .jar or by .jad file.
Example:
In your terminal program enter: AT^SJRA=a:/java/jam/example/helloworld/helloworld.jar
If you prefer to start with .jad file: AT^SJRA=a:/java/jam/example/helloworld/helloworld.jad
The Flash file system on the module is referenced by “a:”.
In your terminal program enter: AT^SJRA=a:/java/jam/example/helloworld/helloworld.jar
If you prefer to start with .jad file: AT^SJRA=a:/java/jam/example/helloworld/helloworld.jad
The Flash file system on the module is referenced by “a:”.
Depending on which file you specify the java application manager tries to find the correspond-
ing file in the same directory. This search is not done by name, but by comparing the contained
attributes. The first file which contains the same values for MIDlet-Name, MIDlet-Version and
MIDlet-Vendor is used.
ing file in the same directory. This search is not done by name, but by comparing the contained
attributes. The first file which contains the same values for MIDlet-Name, MIDlet-Version and
MIDlet-Vendor is used.