Depending on the application type you are deploying, there are different methods to ensure all application and runtime artifacts are downloaded over-the-air (OTA), then stored or installed on the device, without requiring a physical connection the corporate LAN.
Review the various options you can use. Options are organized according to the application type and device target. For larger client bases, Sybase recommends an OTA method where the artifacts are pushed to the device, or are pulled by the user via a URL or link. Generally speaking, hard connection options are best reserved to small deployments or development testing purposes.
| Device Application | Method | Details |
|---|---|---|
| BlackBerry native – once applications provisioned and installed, the application appears in Downloads. However, device users can move it to a different location. If device users reinstall the application from a link or URL, or using Desktop Manager, the BlackBerry device remembers the installation location. |
BlackBerry Enterprise Server (BES) push notifications | When the BlackBerry device activates, it automatically pairs with the BES and downloads the application. See http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB03748 for step-by-step instructions. Also see BlackBerry Provisioning with BES in System Administration. |
| URL/link to installation files | The administrator stages the OTA files in a Web-accessible location and notifies BlackBerry device users via an e-mail message with a link to the JAD file. |
|
| iOS native – users of iPhones tend to self-manage their devices: device users download application files to their iOS devices and synchronize updates as required. As Administrator, you must ensure users are notified of required downloads. | Apple Push Notification Service (APNS) | APNS allows users to receive notifications on iPhones. Each application that supports APNS must be listed in Sybase Control Center with its certificate and application name. See Provisioning with iOS APNS in System Administration. |
| Messaging native applications – may require direct connections either on the LAN or WIFI. This connection prevents man-in-the-middle attacks that might otherwise occur. | Direct Unwired Server connections | If you are not using Afaria for messaging clients, you must first install the client application then connect to corporate LAN using WIFI or any other method of your choosing in order to provision devices with required files. See Provisioning with Unwired Server in System Administration. |
| Hybrid Web Container – because this native application embeds a browser control supplied by the device OS, these devices require specific provisioning techniques. | Configuration Files | The Hybrid Web Container supports only the provisioning from a file method. Provisioning of the Hybrid Web Container provisions the container itself (and therefore all the apps in the container). See Provisioning with Configuration Files in System Administration. |
| Heterogeneous applications (including online data proxy and DOEC) –if you are supporting a heterogeneous device environment, these methods are the best way to provision all devices using the same method. Which method you choose depends on whether or not you want devices connecting directly to Unwired Server. |
Afaria and Configuration Files | Automate the process of provisioning applications by enabling a group of applications to be initially provisioned with a set of parameters from a configuration file using Afaria. See Provisioning with Afaria in System Administration. |
| Windows, Windows Mobile, and BlackBerry | Desktop Management and cradle | Installs the native application when the device is synchronized via a computer. See your device documentation for details. |