Once you have created a mobile application, associated it with the appropriate template, and performed the tasks described in Before Deploying Mobile Applications, you can deploy the mobile application. Keep in mind whether devices are used in online or offline mode as the deployment methods for online and offline mode varies:
Online mode – to make the application available in online mode, create a page and page group combination for the application. The page and page group creates a container for the application, making it available to browsers running in online mode. For example, BlackBerry, Symbian/J2ME, Pocket PC, and so forth. Typically, you should create a page/page group for every application.
Offline mode (PDAs) – to make a mobile application available to mobile devices in offline mode, you must deploy to MobiLink. To do so:
Right-click the approved mobile application(s) you want to deploy, and select Deploy to Mobile Devices. You can select and deploy multiple mobile applications.
In the Deploy Mobile Applications dialog, select Deploy Mobile Applications to MobiLink, and select Mark Offline.
Click Finish.
Offline mode (BlackBerry and Symbian/J2ME) – to make an application available to BlackBerry and Symbian/J2ME clients in offline mode, you must select the “Make available for disconnected mobile devices” option on the Mobile tab.
Mobile applications that are available for offline devices display this icon
.M-Business (connected and disconnected) – to make an application available to M-Business clients, you must deploy to M-Business through public or group channels. The mobile applications are stored in the M-Business Anywhere AGDB database, and deployed to mobile devices when the user logs on, either in connected or disconnected mode depending on the mobile device capabilities.
Note
You see the M-Business deploy options only if you have configured the MB.Enabled property in the global.properties.xml fie. See M-Business Profile View.
Deploying to non-BlackBerry devices using M-Business
Right-click the approved mobile application, select Deploy to Mobile Devices, and choose one of the following:
Create Public Channel – deploys the mobile application into an M-Business public channel. See Deploying to an M-Business Public Channel.
Create Group Channel – deploys the mobile application into an M-Business group channel. See Deploying to an M-Business Group Channel.
Your next step is to deploy and sync the mobile application to the mobile device. See After Deploying Mobile Applications.
Deploying to BlackBerry devices
Once you create the application, you must perform the deploy/sync operation. This is documented in the Unwired Accelerator Quick Start Guide.
Deploying the Unwired Accelerator client files to a BlackBerry device
The Deploy BlackBerry wizard allows you to deploy the Unwired Accelerator Blackberry client files to your BlackBerry device. To access the Deploy BlackBerry wizard:
Right-click the mobile application and select Deploy to Mobile Devices.
Select Deploy the Unwired Accelerator BlackBerry client. This option is available only if the file, blackberry.properties exists in the com.sybase.epclient plugin directory, which is created by the installation program. The installation program checks for the existence of the BlackBerry simulator and the BlackBerry desktop, and adds those directories to the blackberry.properties file.
Click Next. The Deploy BlackBerry wizard opens.
The blackberry.properties file may look similar to:
BlackberryDesktopDir=C:\\Program Files\\Research In Motion\\BlackBerry BlackberrySimulatorDir=C:\\Program Files\\Research In Motion\\BlackBerry JDE 4.0.2\\simulator RemoteLocation=ota\\bb\\direct BlackberryFiles=uaclient.alx,uaclient.cod,uaframework.alx,uaframework.cod,ualistener.alx,ualistener.cod
Specify the directories for the simulator and the desktop. The default directories are provided based on the contents of the blackberry.properties file. Select Browse to change the entries. When you click Finish, the selected .cod and .alx files are downloaded from the server to the specified directories. You need to do this only once. If you select Deploy BlackBerry at a later time, the Override option allows you to overwrite the .cod and .alx files.
For the desktop from which you are deploying/syncing, download the files to the BlackBerry device.