Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
You can create a provisioning file by either modifying an existing template XML file or creating a new XML file. The XML file must be UTF-8 encoded.
Note: |
---|
An optional Device Configuration Manager tool is available as a
part of the Mobile Operator Technical Resource Kit. This tool will
help you to create XML files that you can use to configure the
device. The Mobile Operator Technical Resource Kit is available for
download from
|
The syntax of the provisioning file is dependent upon the protocol you use to manage devices. The following list shows the protocols used:
- OMA Client Provisioning -- Typically used for bootstrapping a
device, this method is a one-way Wireless Application Protocol
(WAP) push. For more information, see
MSPROV DTD
Formatand
OMA Client
Provisioning XML File Examples.
- OMA Device Management (DM) -- Used for continuous provisioning,
this method uses two-way communication between the server and the
device. OMA DM commands are transmitted between the server and the
client device in messages. A message can contain one or more
commands. For a list of supported commands, see
OMA DM Protocol
Command Elements.
For information about OMA DM XML syntax, see OMA DM Provisioning Filesand OMA DM Provisioning XML File Examples.
For information about the provisioning file syntax for different OMA Client Provisioning versions, see OMA Client Provisioning Files.
To Create an OMA Client Provisioning XML file
-
Copy the following information into a text editor:
Copy Code <wap-provisioningdoc> <!-- write or paste OMA Client Provisioning XML code snippet for the first Configuration Service Provider here --> <!-- write or paste OMA Client Provisioning XML code snippets for a second Configuration Service Provider here --> </wap-provisioningdoc>
-
Save the file as < filename>.provxml.
Note: Microsoft recommends that you use a three-digit version number in the name of your .provxml files in ROM, such as mxip_opr_100, mxip_opr_200, mxip_opr_300, so that there is an adequate number of ordinals to identify successive versions of the file. For more information about file naming, see Provisioning Using a ROM Configuration XML File.
-
Write or paste the desired OMA Client Provisioning XML into a file as described in OMA Client Provisioning Files.
For examples of OMA Client Provisioning XML code, see OMA Client Provisioning XML File Examples.
-
Save the file.
You should test that the provisioning XML makes the desired changes to a Windows Mobile device similar to the ones that you want to update.
To Create an OMA DM Provisioning XML file
-
Before you can use OMA DM, you must have obtained access to or set up an OMA DM Server.
-
Copy the following information into a text editor:
Copy Code <SyncML xmlns='SYNCML:SYNCML1.1'> <SyncHdr> <VerDTD>1.1</VerDTD> <VerProto>DM/1.1</VerProto> <SessionID>1</SessionID> <MsgID>1</MsgID> <Target> <LocURI>{Unique device ID}</LocURI> </Target> <Source> <LocURI>https://www.thephone-company.com/mgmt-server</LocURI> </Source> </SyncHdr> <SyncBody> <!-- comment about what change the following code makes --> <!-- write or paste XML code snippets here --> <Final /> </SyncBody>
-
Replace the SyncHdr information as appropriate per OMA DM Provisioning Files.
-
Write or paste the desired OMA DM XML code
For examples of OMA DM XML code, see OMA DM Provisioning XML File Examples.
-
Save the file.
-
Wrap the XML in an OMA DM message.
You should test that the provisioning XML makes the desired changes to a Windows Mobile device similar to the ones that you want to update.
To create an XML file that you will send in a CAB or .cpf file
-
Create an XML file that uses any XML syntax.
-
Save the file as <filename>_setup.xml