Description Property
Number of devices registered in Mobile Device Manager that matches this model type.
Note
This field is only displayed on theModel Detailpage, not when creating or editing model properties.
#Devices
The remaining properties are for DM models only.
Currently supported OMA DM versions are 1.1 and 1.2.
OMA DM Version
The type of DM server authentications. Possible values are:
DM Server Authentication
■ Use Tenant Setting. Uses the specified tenant setting for server authentication. ■ None. No authentication.
■ Basic. HTTP authentication in which the subscriber authenticates by presenting
credentials consisting of a user name/password pair. See RFC2617 (http:// www.faqs.org/rfcs/rfc2617.html).
■ Digest. HTTP authentication in which the subscriber authenticates by presenting
credentials consisting of an MD5 digest. See RFC2617 (http://www.faqs.org/rfcs/ rfc2617.html).
■ HMAC. A mechanism for the subscriber to authenticate by using cryptographic
hash functions. See RFC 2104 (http://www.faqs.org/rfcs/rfc2104.html). Type ofbootstrapnotification. Possible values are:
Bootstrap Type
■ WAP. This profile defines a number of parameter extensions to the WAP
Provisioning Content Format. This profile also defines how these and other parameters are mapped in to the DM management object. This type is recommended.
■ plain. This profile specifies how the SyncML DM management object can be
bootstrapped using a SyncML DM format. For security, it leverages the methods developed for WAP Provisioning.
The bootstrap message content-type is Encoded when this box is checked.
Note
If you do not set this value by checking the box, the device user is not prompted to enter a PIN number, and the mobile device displays a message stating:
Use Encoding for Bootstrap Message
the message received is from an untrusted server
159
Viewing models
Model Detail properties (continued)
Description Property
Credentials computed for HMAC authentication use the nonce sent in each package if this box is checked.
Use New Nonce per package
Some models support Large Objects. To always support large objects, check this box.
Always support Large Objects
Check this box if the model supports the HTTPS protocol.
Supports HTTPS
URL for device management.
The OMA DM URL
DM properties that are to be set differently than the default should be added here:
Other DM properties
■
supportsAtomic. Eithertrueorfalse; the default istrue.
Use the following properties when creating the Windows Mobile model:
useRealUUID=true;supportsAtomic=true; autoCreatesDynamicChildNodes=true;
Node for where the firmware version is listed. The default is:
./DevDetail/FwV
Firmware Version Node
Type ofFOTA (firmware over-the-air)download. Possible values are:
FOTA Download Method
■ FOTA Download Not Supported. ■ Inline Download.
■ Alternate Download.
If you selectFOTA Download Not Supported, then the corresponding manufacturer name and/or model are not displayed in the search for devices in theUpdatestab and in the searches inProvisioning->Assign Image to Deviceand
Provisioning->Assign Image to Multiple Devices. This also applies toDevice Detail->Assign Image.
If you select Inline Downloador Alternate Download, then you also have to provide the values for these fields:
■ Firmware Update Node
■ The Node to Replace during a FOTA operation ■ The Node to Exec during a FOTA operation
■ The Node that has the result of the FOTA operation
Managing Models
160
Model Detail properties (continued)
Description Property
In addition to these fields, you must provide the firmware upgrade package by using
Updates->Upload Update Packagesfor the models to be displayed in the search. The root node that is to be replaced during the FOTA. SeeFOTA Download Method
for more information.
Firmware Update Node
The node containing the image binary data. SeeFOTA Download Methodfor more information.
The Node to Replace during a FOTA operation
The note that triggers the firmware upgrade. SeeFOTA Download Methodfor more information.
The Node to Exec during a FOTA operation
The node showing the success or failure of the upgrade operation. SeeFOTA Download Methodfor more information.
The Node that has the result of the FOTA operation
A template that accommodates variations required by the implementation of some model’s bootstrap process. Templates for both plain and WAP bootstrap types define
Bootstrap Template
parameter values for various bootstrap characteristics. For examples of WAP and plain bootstrap templates, see“Bootstrap Template Examples” on page 262.
At the bottom of theModel Detailpage, the buttons for functions that may be performed on the selected model are listed:
■ Manage DDF. Uploads manufacturer-specified device definition files (DDFs) for a model’s supported services and
features. Once the files are on theMDM Server, you can view them in a hierarchical tree format. See“Managing DDFs” on page 258for more details.
■ Manage Profile Mappings. Displays the profile mapping details for a particular model. The model mapping shows
the node relative paths for all defined attributes defined by a particular profile.
■ In addition, the generic profile template can also be viewed, which is unmapped, yet shows the details of each profile
attribute (that is, attribute types, default values, whether multi-values, user attributes, displayed, required, or unique values). See“Modifying a profile” on page 150for more details.
■ Edit. Edits the model details. See“Editing model properties” on page 162.
■ Delete. Deletes the model. See“Deleting a model” on page 162.