NAPDEF Configuration Service Provider Examples for OMA Client Provisioning
The NAPDEF Configuration Service Provider adds, modifies, and deletes WAP network access point definitions (NAPDEFs) and their settings, by using WAP techniques or standard device techniques.
You can only add a NAP using the standard format (WAP technique). Device technique is the Microsoft format that promotes the ID parm into a characteristic around the other parms and subcharacteristics. In this Configuration Service Provider, the ID parm is NAPID.
The following examples can be used as templates to configure settings for the NAPDEF Configuration Service Provider. Below the NAPDEF characteristic type, replace the value for each parm and characteristic type with values that correspond to your system. Not all possible parameters and characteristics appear in the examples.
Note The Microsoft format for NAPDEF contains the provisioning XML attribute mwid. This custom attribute is optional when adding a NAP or a proxy. It is required when updating and deleting existing NAPs and proxies and must have its value set to 1.
- Adding a NAPDEF (WAP Technique) Example
- Adding and Modifying a NAPDEF (Device Technique) Example
- Deleting a NAPDEF (Device Technique) Example
See Also
NAPDEF Configuration Service Provider | Bootstrapping To Use an OMA Client Provisioning Server
Send Feedback on this topic to the authors