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. |
4/8/2010
In this example, a device is configured to enable the synchronization of Tasks.
Code Example
1. Query for the Sync "Sources": GUID. Use this query XML:
Copy Code | |
---|---|
<characteristic type="Sync"> <characteristic-query recursive="false" type="Sources"/> </characteristic> |
Note: |
---|
It should return a GUID which will be used in the next step. |
2. Use the Sources GUID in this XML. Replace <{GUID}> with the actual GUID found in step 1:
Copy Code | |
---|---|
<characteristic type="Sync"> <characteristic type="Sources"> <characteristic type="<{GUID}>"> <characteristic type="Engines"> <characteristic type="{22C7DA12-F3FD-4875-8344-7786454F6534}"> <characteristic type="Providers"> <characteristic type="{783ae4f6-4c12-4423-8270-66361260d4f1}"> <parm name="Enabled" value="1"/> </characteristic> </characteristic> </characteristic> </characteristic> </characteristic> </characteristic> </characteristic> |
Note: |
---|
The GUID is generated at run time, meaning it is different for different devices. Hence the need to determine it before enabling or disabling Tasks. |
Remarks
One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must replace the values as appropriate, and add the node as a child of the OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.