Share via


Create an OMA DM Account

4/8/2010

This example shows how to create a new account and set up the 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 in.

Code Example

<Atomic>
  <CmdID>2</CmdID>
  <Add>
      <CmdID>3</CmdID>
      <Item>
      <Target>
          <LocURI>./SyncML/DMAcc/<NewNode>/<Name></LocURI>
      </Target>
      <Data><New Account> </Data>
  </Item>
  </Add>
 
  <Add>
      <CmdID>4</CmdID>
      <Item>
          <Target>
              <LocURI>./SyncML/DMAcc/<NewNode>/<AppAddr></LocURI>
          </Target>
          <Data>www.<myserver>.net/manage</Data>
      </Item>
  </Add>

  <Add>
      <CmdID>5</CmdID>
      <Item>
          <Target>
              <LocURI>./SyncML/DMAcc/<NewNode>/<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.

See Also

Concepts

DMAcc Configuration Service Provider Examples for OMA DM