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

If the provisioning XML file is in a signed .cab or .cpf file, you can automatically download the file using Service Loading (SL). Service Loading is a WAP push feature. For more information, see SI and SL XML Files.

Note:
Security roles can impact the configuration result. For information on role-based access control, see OMA Client Provisioning Security Best Practices.

The SL message is sent in connectionless unsecure WAP push operations from the Push Proxy Gateway, which encodes it by using WAP Binary XML (WBXML) tokens.

Depending on the action level, which is specified in the actionattribute of an SL message, the SL message is processed in different ways:

The following illustration shows a graphical view of how the provisioning XML is pulled to the device by using SL.

For a description of the user experience with SL, see SI and SL Notifications Behavior.

To push XML OTA by using SL

  1. Put the .cab or .cpf file that contains the provisioning XML file on a web site from which the user can download the file.

  2. Create the SL XML file to send a message to the user.

    SL messages are simple XML files, so you can create them in any text editor. For proper syntax, see SL Message Format.

  3. Send the SL message to the user.

    Note   The user may or may not be aware that an update is available, depending on the action level and how the device processes the message.

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.