Deploying the Provisioning File

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

1. Copy the provisioning file to the device:
   • Android devices: 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.”).
   • BlackBerry devices: 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 – client supports provisioning only through Afaria client deployment.
   • Windows Mobile devices: 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 devices: 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).
   • When provisioning the Hybrid Web Container on a device:
     • Android – the Android client searches the root of the flash card ("/sdcard/"), followed by the client file root (“/data/data/com.sybase.workflow/files.”).
     • BlackBerry – the BlackBerry client searches the root of the flash card (“fileconn.dir.memorycard”), followed by the client file root (“file:///store/home/user/”).
     • iOS – client supports provisioning only through Afaria client deployment.
     • Windows Mobile – the Windows Mobile client searches the root of any flash cards, followed by the root of the file system.
2. Register the application connection:
   • For device clients, log in to Sybase Control Center and register the application connection as described in the topic Registering and Reregistering a Connection in System Administration.
   • For Mobile Workflow clients, log in to Sybase Control Center and register the Mobile Workflow application connection as described in the topic Registering and Reregistering Mobile Workflow Application Connections in Developer Guide: Mobile Workflow Packages.
3. Start the application.
   When the application is started, a search is performed for the provisioning file only if the device is not yet configured. Unconfigured is defined as missing one or more of the required connection properties (server name, port, user name, activation code, and so on). If unconfigured, the settings from the provisioning file are automatically applied.