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. |
OMA DM version 1.2 defines a Generic Alert message for alerts generated by the client that have a relation to a Management Object. The Source and LocURI identify the address to the Management Object. The alert code for the generic alert is 1226.
Note: |
---|
In Windows Mobile 6, the OMA DM generic alert is used only for Firmware Update Managed Object (FUMO). |
The client can send a Generic Alert message (1226) to the server any time after there is a client- or server-initiated management alert (after execution of the Managed Object). The server responds with the status for how the server handles all items in the package.
For Windows Mobile devices, multiple generic alerts are sent by multiple Alert elements.
Code Example
The following example shows how a generic alert (1226) is used for an OMA Firmware Update Managed Object (FUMO) in a Windows Mobile device.
Copy Code | |
---|---|
<Alert> <CmdID>2</CmdID> <Data>1226</Data> <!-- alert code for Generic Alert --> <Correlator>abc123</Correlator> <Item> <Target> <LocURI>sample_uri</LocURI> </Target> <Source> <LocURI>./FwUpdate/Package1/DownloadAndUpdate</LocURI> </Source> <Meta> <Type xmlns="syncml:metinf"> org.openmobilealliance.dm.firmwareupdate.downloadandupdate </Type> <!-- This generic alert is for the Exec command that is sent to the FUMO object's DownloadAndUpdate node --> <Format xmlns="syncml:metinf">int</Format> </Meta> <Data>200</Data> </Item> </Alert> |
Comments
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.
The following table shows the supported elements.
Elements | Description |
---|---|
CmdID |
Specifies the unique identifier for an OMA DM command. |
Data |
Specifies the alert type 1226 for generic alert. |
Correlator |
Is used when the alert is an asynchronous response to an Exec command. Typically, this element echoes the Correlator value from an Exec command and is omitted in all other instances. |
Item |
Holds alert information. Windows Mobile devices support one item in a generic alert. |
Target |
Specifies the location at which the device has installed the downloaded package; this package was downloaded using the Download Configuration Service Provider. This URI is a unique device ID, so there can be only one target for each item. |
Source |
Specifies the LocURI, a unique device ID, of the management object node that needs this generic alert. There can only be one source for each item. |
Meta |
Holds meta information that supports the Data element. There can be one Meta tag for each Item |
Type |
Specifies the media type of the information in the Data element. In this case, the information is a Uniform Resource Name (URN). There can be one Type tag inside a Meta tag. |
Format |
Required. Contains a SyncML identifier of the format of the Data element. There can be one Format element inside a Meta tag. |
Data |
Specifies the OMA FUMO result code that is the generic alert data. For a list of valid codes and their meaning, see OTA Firmware Update Result Codes. There can be one Data element inside an Item. |