Siemens AC65 User Manual
Java User’s Guide
9.2 Compile
66
s
wm_java_usersguide_v12
Page 65 of 123
2008-02-25
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 examples directory, \Siemens\SMTK\<productname>
\wtk\src\example.
Compile the program with the SDK. Examples of build batch files can be found in each sam-
ple program found in the examples directory, \Siemens\SMTK\<productname>
\wtk\src\example.
•
If the compile was successful the program can be run from the command line. Examples of
run batch files can be found in the examples directories listed above as well.
run batch files can be found in the examples directories listed above as well.
The batch files for compiling and running the samples refer to master batch files in the …\Sie-
mens\SMTK\<productname>\wtk\bin directory and use the system environment variables
IMPNG_JDK_DIR and IMPNG_DIR. IMPNG_JDK_DIR points to the root directory of the
installed JDK and IMPNG_DIR points to the root directory of the Siemens-SMTK-<product-
name>-IMPNG installation. The installation process sets these environment variables. A mod-
ification is usually not necessary. They may be modified as requested (e.g. when switching to
a different JDK) via the advanced system properties.
mens\SMTK\<productname>\wtk\bin directory and use the system environment variables
IMPNG_JDK_DIR and IMPNG_DIR. IMPNG_JDK_DIR points to the root directory of the
installed JDK and IMPNG_DIR points to the root directory of the Siemens-SMTK-<product-
name>-IMPNG installation. The installation process sets these environment variables. A mod-
ification is usually not necessary. They may be modified as requested (e.g. when switching to
a different JDK) via the advanced system properties.
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.