Partager via


Download and Install Example

4/8/2010

The following XML example can be used as a template to configure the Download Configuration Service Provider.

This example shows how to add the characteristics and parameters to download and install an application.

Code Example

<Add>
  <CmdID>2</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/SwMgmt/Download/{group1}/PkgID</LocURI>
    </Target>
    <Data>{pkgid1}</Data>
  </Item>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/SwMgmt/Download/{group1}/PkgURL</LocURI>
    </Target>
    <Data>{package download server HTTP address}</Data>
  </Item>0
</Add>
<Exec>
  <CmdID>3</CmdID>
  <Item>
    <Target>
      <LocURI>./Vendor/MSFT/SwMgmt/Download/{group1}/Operations/DownloadInstall</LocURI>
    </Target>
  </Item>
</Exec>

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.

For this example, replace the information enclosed in braces {} with correct values for your system. The following table shows the meaning of the information that you must replace.

String to replace Meaning

{group1}

An identifier for the download parameters.

{pkgid1}

A device unique identifier for the download package.

{package download server HTTP address}

The URI for the downloadable component.

See Also

Reference

Download Configuration Service Provider

Concepts

Download Configuration Service Provider Examples for OMA DM