OMA Client DM xml format and SyncML questions

[allen]

Hi,
A couple of device provisioning questions...

OMA Client DM xml format questions:
When I attempt to query for device information, the command states that it
successfully completes, but the output file that is generated is an exact
copy of my input file?? Below is the xml command I am attempting to push

<wap-provisioningdoc>
<characteristic type="DeviceInformation">
<parm-query name="Product" />
<parm-query name="AvailableRam" />
<parm-query name="TotalRam" />
<parm-query name="AvailableStorage" />
<parm-query name="TotalStorage" />
<parm-query name="BacklightACTimeout" />
<parm-query name="BacklightBatteryTimeout" />
<parm-query name="BatteryStrength" />
<parm-query name="ProcessorType" />
<parm-query name="ProductVersion" />
<parm-query name="OperatingSystem" />
<parm-query name="OperatingSystemVersion" />
</characteristic>
</wap-provisioningdoc>

Other queries (i.e., security settings, certificates, ...) work as expected,
but this and a simple query of the alarm status return the input files as
their output.

SyncML questions:
I am attempting to build OMA DM compliant xml commands and apply them to my
mobile devices (both smart phone and pocket pc) using rapiconfig.exe, but
whenever i attempt to push this xml command to the device, i always receive a
"Config failed (0x80004005): Unspecified error" error message. Below is the
SyncML that I am trying to push

<SyncML xmlns='SYNCML:SYNCML1.1'>
<SyncHdr>
<VerDTD>1.1</VerDTD>
<VerProto>SyncML/1.1</VerProto>
<SessionID>1</SessionID>
<MsgID>1</MsgID>
<Target>
<LocURI>IMEI:35638400546326800</LocURI>
</Target>
<Source>
<LocURI>localhost</LocURI>
</Source>
</SyncHdr>
<SyncBody>
<Get>
<CmdID>2</CmdID>
<Item>
<Target>
<LocURI>./DevInfo</LocURI>
</Target>
</Item>
</Get>
<Final />
</SyncBody>
</SyncML>

Thank you in advance for your help,
allen

[Bill Stelzel [MSFT]]

For the first question I'll bet that you are trying this on a Pocket PC
device. It's easy to miss but there is a not in the documentation for the
DeviceInformation Configuration Service Provider that says "This
Configuration Service Provider can be managed in Smartphone only." This
configuration service provider is not present on the Pocket PC.

Anticipating the next question -- Why isn't an error returned in this case?
There is no error returned because the protocol specification says that
unrecognized elements in the configuration document are to be ignored. This
is to allow management servers to send configuration documents that contain
provisioning elements for all the devices they support and the device will
act on those elements it recognizes and ignore the rest.

For your second question rapiconfig only works with WAP provisioning docs
and cannot be used to process SyncML documents.

--
Bill Stelzel [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

"allen" <al...@discussions.microsoft.com> wrote in message
news:5B507613-99AF-4661...@microsoft.com...

[allen]

Hi Bill,
Thank you for your response to my questions regarding DeviceInformation and
the lack of SyncML support in rapiconfig.

I do have another question that you or maybe someone else in this group can
help to answer. Where can I find the authoritative document(s) and/or
examples regarding SyncML other than the specs on the OMA site? I've got the
mobile operators guide, and both the current ppc and sp sdk's but the
information is a bit limited.

Thanks again,
Alle

[Bill Stelzel [MSFT]]

The source you mention are probably the best. Also the SDK docs are now
available at http://msdn.microsoft.com and will be updated on a regular
basis so there may be newer information there than in the SDK.

Are there specific questions you have or are you just looking for more of an
overview of syncML support on Windows Mobile?

--
Bill Stelzel [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.

"allen" <al...@discussions.microsoft.com> wrote in message

news:C3822BF6-CA49-420C...@microsoft.com...

[pierrick...@gmail.com]

Hi,

I suggest that you give the OMA-DM simulator provided by Koneki (Eclipse
open source project) a try:
http://www.eclipse.org/koneki/simulators/omadm/.
Its documentation contains links to the official OMA-DM specification, and
instructions on how to use it with Funambol OMA-DM server.
By using the simulator, you should be able to intuitively learn more about
the OMA-DM messages exchanged between an OMA-DM client and a server.
Feel free to use the Koneki forum to give feedback regarding the tool.

Pierrick.