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

The following XML shows how perform the following tasks:

Code Example

Copy Code 
<Add>
   <CmdID>1</CmdID>
   <Item>
	 <Target>
		 <LocURI>./FwUpdate/{package
identifier}/DownloadAndUpdate/PkgURL</LocURI>
	 </Target>
	 <Data>http://{package download server http
address}/{update_package.pks}</Data>
   </Item>
   <Item>
	 <Target>
		 <LocURI>./FwUpdate/{package
identifier}/PkgName</LocURI>
	 </Target>
	 <Data>{package name}</Data>
   </Item>
</Add>
<Exec>
   <CmdID>2</CmdID>
   <Item>
	 <Target>
		 <LocURI>./FwUpdate/{package
identifier}/DownloadAndUpdate</LocURI>
	 </Target>
	</Item>
</Exec>

Remarks

One provisioning XML file typically contains configuration information for multiple Configuration Service Providers. To use this example, you must do the following:

  • Add the example XML 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.

  • Replace the information in braces ({}) with correct values for the package. The following table shows the meaning of the information that you must replace.

String to replace Meaning

{package identifier}

A unique identification for the package.

{update_package.pks}

The name and extension of the update package.

In this example, the package has an extension of .pks, meaning that it is a super package.

{package download server HTTP address}

The GUID of the Image Update Download Package Server.

{package name}

The user friendly name of the package to be downloaded.

See Also