Distributing and Loading the Application Provisioning File

Make the provisioning file available to the device so that it can be automatically loaded when the application starts.

When the application is started, a search is performed for the provisioning file only if the device is not yet configured; that is, missing one or more of the required connection properties (server name, port, user name, activation code, and so on). If the application is unconfigured, the settings from the provisioning file are automatically applied.

Deliver the application provisioning file to the device and make it available to load when the application starts.

Methods of delivery vary:

Android – use e-mail or messaging to upload the provisioning file to the root of the flash card (/sdcard/), or the client file root (/data/data/com.sybase.workflow/files).
Note: Some Android devices, for example, Samsung, have built-in storage with the folder name "sdcard," so even if there is not an SD card inserted in the device, you can still see an sdcard directory. The provisioning file does not work in the sdcard directory unless there is an SD card inserted in the device.
BlackBerry – use BES push, e-mail, or messaging to upload the provisioning file to the root of the flash card (fileconn.dir.memorycard), or the client file root (file:///store/home/user/).
iOS – Afaria client deployment.

Windows Mobile – use e-mail or messaging to upload the provisioning file to the client root of any flash cards, or the root of the file system.
Win32 – use e-mail or messaging to upload the provisioning file to the Application Data subdirectory which resides in the Special Folder path defined by CSIDL_APPDATA (%APPDATA%\Sybase\MOMessaging).
Hybrid Apps – Delivery is not applicable. Searches and loads files by as previously described for each operating system.