Java User’s Guide
8.5 Java File Format
63
s
wm_java_usersguide_v12
Page 58 of 123
2008-02-25
Confidential / Released
The values of APPDIR, BEARER and START are used internally and must be lower case. The
password (PWD) is case sensitive. The case sensitivity of the other parameter values depends
on the server application or the network. It is likely that not all parameters can be sent in one
SM. They can be distributed over several SMs. Every SM needs to contain the identifying first
line (OTAP_IMPNG) and the PWD parameter if a mandatory password has been enabled.
OTAP is started when the keyword START, possibly with a parameter, is contained in the SM
and the parameter set is valid for the requested operation. It always ends with a reboot, either
when the operation is completed, an error occurred, or the safety timer expired. This also
means that all parameters previously set by SM are gone.
Apart from the first and the last line in this example, these are the parameters described in the
previous section. Possible parameters for the START keyword are: “install”, “delete” or nothing.
In the last case, an install operation is done by default.
The network does not guarantee the order of SMs. So when using multiple SMs to start an
OTAP operation their order on the receiving side might be different from the order in which they
were sent. This could lead to trouble because the OTAP operation might start before all param-
eters are received. If you discover such problems, try waiting a few seconds between each SM.
8.5
Java File Format
In general, all Java files have to comply with the IMP-NG and ME specifications. There are cer-
tain components of the JAD file that the developer must pay attention to when using OTAP:
•
MIDlet-Jar-URL: make sure that this parameter points to a location on the network where
your latest JAR files will be located, e.g.
http://192.168.1.3/datafiles/mytest.jar
, not in the
filesystem like
file://a:/java/mytest/mytest.jar
. Otherwise this JAD file is useless for OTAP.
•
MIDlet-Install-Notify: this is an optional entry specifying a URL to which the result of an
update/install operation is posted. That is the only way to get any feedback about the out-
come of an install/update operation. The format of the posted URL complies with the IMP-
NG OTA Provisioning specification. In contrast to the jar and jad file this URL must not be
protected by basic authentication.
•
MIDlet-Delete-Notify: this is an optional entry specifying a URL to which the result of a
delete operation is posted. That is the only way to get any feedback about the outcome of
a delete operation. The format of the posted URL complies with the IMP-NG OTA Provision-
ing specification. In contrast to the jar and jad file this URL must not be protected by basic
authentication.
•
MIDlet-Name, MIDlet-Version, MIDlet-Vendor: are mandatory entries in the JAD and Man-
ifest file. Both files must contain equal values, otherwise result 905 (see
Section 8.7
) is
returned.
•
MIDlet-Jar-Size must contain the correct size of the jar file, otherwise result 904 (see
Sec-
tion 8.7
) is returned.
Example:
MIDlet-Name: MyTest
MIDlet-Version: 1.0.1
MIDlet-Vendor: TLR Inc.
MIDlet-Jar-URL: http://192.168.1.3/datafiles/MyTest.jar
MIDlet-Description: My very important test
MIDlet-1: MyTest, , example.mytest.MyTest
MIDlet-Jar-Size: 1442
MicroEdition-Profile: IMP-NG
MicroEdition-Configuration: CLDC-1.1
