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. |
This example shows how to create a new OMA DM v1.2 account, and set up the OMA DM v1.2 management server address. In this example, three ADD commands are nested inside an ATOMIC command, so all three must succeed for the entire xml provisioning document to succeed. If any ADD command fails, then all changes are rolled back and the device is left in the state it began.
Code Example
Copy Code | |
---|---|
<Atomic> <CmdID>2</CmdID> <Add> <CmdID>3</CmdID> <Item> <Target> <LocURI>./SyncML/DMS/<x>/Name</LocURI> </Target> <Data>New Account</Data> </Item> </Add> <Add> <CmdID>4</CmdID> <Item> <Target> <LocURI>./SyncML/DMS/<x>/AppAddr/x/Addr</LocURI> </Target> <Data>www.myserver.net/manage</Data> </Item> </Add> <Add> <CmdID>5</CmdID> <Item> <Target> <LocURI>./SyncML/DMS/<x>/ServerID</LocURI> </Target> <Data>www.mgmtserver.com</Data> </Item> </Add> </Atomic> |
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 SyncBody node in an OMA DM provisioning file. For more information about the syntax of the provisioning file, see OMA DM Provisioning Files.
The following table shows the information that you must enter for this example to work.
Replace | With | ||
---|---|---|---|
<NewNode> |
The identifier of the OMA DM v1.2 account.
|
||
<New Account> |
The user-readable name of the new account. |
||
www.<myserver>.net/manage |
The address of the server to be added. |
||
www.<mgmtserver>.com |
The server identifier for the current OMA DM v1.2 account.
|