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 example can be used as a template to configure settings for the CM_PlannerConfiguration Service Provider. Below the CM_Planner characteristic type, replace the value for each parameter and characteristic type with values that correspond to your system.

To provision devices using the OMA DM protocol, use the CMPLANNER Configuration Service Providerinstead.

Code Example

The following example sets the preferred connections for each metanetwork that was defined in a CM_Networks Configuration Service Provider.

Copy Code
<characteristic type="CM_Planner" >
  <characteristic type="PreferredConnections">
	<parm name="{436EF144-B4FB-4863-A041-8F905A62C572}"
value="GPRS1" />
	<parm name="{A1182988-0D73-439e-87AD-2A5B369F808B}"
value="PPP1" />
	<parm name="{7022E968-5A97-4051-BC1C-C578E2FBA5D9}"
value="PPP2" />
	<parm name="{F28D1F74-72BE-4394-A4A7-4E296219390C}"
value="PPP3" />
  </characteristic>
</characteristic>

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 OMA Client Provisioning file. For information about the syntax of this file, see OMA Client Provisioning Files. For examples, see OMA Client Provisioning XML File Examples.

See Also

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.